From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: muradm <mail@muradm.net>, "Ludovic Courtès" <ludo@gnu.org>,
56690@debbugs.gnu.org
Subject: [bug#56690] [PATCH] gnu: seatd-service-type: Should use seat group.
Date: Mon, 08 Aug 2022 08:08:53 +0200 [thread overview]
Message-ID: <55a3a3bf118f364b70cbd74d214998955d81eaa9.camel@ist.tugraz.at> (raw)
In-Reply-To: <87h72n24ra.fsf@muradm.net>
Am Sonntag, dem 07.08.2022 um 23:05 +0300 schrieb muradm:
> * gnu/services/desktop.scm (seatd-service-type): Uses "seat" group.
> [extensions]: Added account-service-type with seatd-accounts.
> (seatd-accounts): Conditionally produces list with "seat" group.
> (<seatd-configuration>):
> [user] Drop user field, since it is not going to be used.
Removed field.
> [group] Change default value to "seat".
> [existing-group?] Add field which controls if group should be
> created or not.
Would be Added field, but see below.
> * doc/guix.texi: Mention that users may need to become members of
> "seat" group and update default value for group field. Add
> explanation on seatd.sock file. Remove dropped user field.
> +When seat mamanagement is provided by @code{seatd}, users that
> acquire
management.
> +resources provided by @code{seatd} should have permissions to access
> +its UNIX domain socket. By default, @code{seatd-service-type}
> provides
> +``seat'' group. And user should become its member.
Which user? Closely related, who acquires resources provided by
@code{seatd}? Just the greeter? A regular user logging in?
What access level is needed/provided? Read access? Write access?
> + (group seatd-group (default "seat"))
> + (existing-group? seatd-existing-group? (default #f))
AFAIK this is not necessary. accounts-service-type can handle multiple
eq? groups, so as long as you're careful with what you put into group,
you shouldn't get an error.
Cheers
next prev parent reply other threads:[~2022-08-08 6:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 4:27 [bug#56690] [PATCH] gnu: seatd-service-type: Should use seat group muradm
2022-07-24 16:28 ` ( via Guix-patches via
2022-08-05 8:10 ` Liliana Marie Prikler
2022-08-07 20:45 ` muradm
2022-08-06 20:46 ` Ludovic Courtès
2022-08-06 20:50 ` ( via Guix-patches via
2022-08-08 8:58 ` Ludovic Courtès
2022-08-08 9:12 ` ( via Guix-patches via
2022-08-08 19:44 ` muradm
2022-08-08 18:55 ` muradm
2022-08-07 17:28 ` muradm
2022-08-07 20:05 ` muradm
2022-08-08 6:08 ` Liliana Marie Prikler [this message]
2022-08-08 18:50 ` muradm
2022-08-09 6:57 ` Liliana Marie Prikler
2022-08-09 19:47 ` muradm
2022-08-10 8:07 ` Liliana Marie Prikler
2022-08-13 17:39 ` muradm
2022-08-22 20:17 ` muradm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55a3a3bf118f364b70cbd74d214998955d81eaa9.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=56690@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=mail@muradm.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).