From: "Ludovic Courtès" <ludo@gnu.org>
To: muradm <mail@muradm.net>
Cc: 56690@debbugs.gnu.org
Subject: [bug#56690] [PATCH] gnu: seatd-service-type: Should use seat group.
Date: Sat, 06 Aug 2022 22:46:49 +0200 [thread overview]
Message-ID: <87czdddrra.fsf@gnu.org> (raw)
In-Reply-To: <20220722042745.26745-1-mail@muradm.net> (muradm's message of "Fri, 22 Jul 2022 07:27:45 +0300")
Hi,
muradm <mail@muradm.net> skribis:
> * gnu/services/desktop.scm (seatd-service-type): Uses "seat" group.
> [extensions]: Added account-service-type with %seatd-accounts.
> (%seatd-accounts): List with "seat" group.
> (<seatd-configuration>): [group] Change default value to "seat".
> * doc/guix.texi: Mention that users may need to become members of
> "seat" group and update default value for group field.
I guess I’m missing some context: is this fixing a bug currently
present? (Apologies if this has been discussed elsewhere!)
> +Users which are going to interact with @code{seatd} daemon while logged in
s/which/who/
> +should be added to @code{seat} group. For instance:
> +
> +@lisp
> +(user-account
> + (name "alice")
> + (group "users")
> + (supplementary-groups '("wheel" ;allow use of sudo, etc.
> + "seat" ;interact with seatd
> + "audio" ;sound card
> + "video" ;video devices such as webcams
> + "cdrom")) ;the good ol' CD-ROM
> + (comment "Bob's sister"))
The problem I see with this extra doc is that even I wouldn’t know how
to tell whether I’m going to “interact with seatd”. Fundamentally it’s
not something I really care about. :-)
How could we improve on this? Like, if this is important, should it be
the default?
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-08-06 20:47 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 [this message]
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
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=87czdddrra.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=56690@debbugs.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).