From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: muradm <mail@muradm.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 56690@debbugs.gnu.org
Subject: [bug#56690] [PATCH] gnu: seatd-service-type: Should use seat group.
Date: Wed, 10 Aug 2022 10:07:07 +0200 [thread overview]
Message-ID: <feefa8add73babb6fb99636e1e676b1eae309c89.camel@ist.tugraz.at> (raw)
In-Reply-To: <87y1vxxjrt.fsf@muradm.net>
Am Dienstag, dem 09.08.2022 um 22:47 +0300 schrieb muradm:
> There is no such specification as login manager or what ever. User
> is any one/thing acquiring resources via seat management. It is
> perfectly fine to run mingetty, login into bash and from command line
> start sway that will use libseat to acquire video for instance. Who is
> user here?
>
> There is also no display manager as it was before. Please see my
> explanation to unmatched-paren:
> https://debbugs.gnu.org/cgi/bugreport.cgi?msg=46;bug=56690
> What is sway in this usecase, it is not a user (like you or me),
> it is not a display manager (as gdm, sddm etc.). It is just
> application requiring video card (not only) resource, which
> it instead of having exclusive root access, uses libseat to
> acquire it in "seat managy" way. And greetd does/should not
> care about seatd/libseat until it is not required to acquire
> resources in "seat managy" way. Instead it is a greeter which
> is totatly customizable, could be even a bash script or small
> suckless-like application or else.
>
> This is the point of seatd I suppose, to do one thing only
> without enforcing on who should do what.
>
> Thus, none of your proposals are suitable, and I can't come up
> with something better than "seat management user" or "libseat
> user". However in my opinion, the one who commits into such
> setup, should be aware of what is seatd libseat and how, why to
> interact with it.
I think you're mixing user and application here, which makes explaining
this to others difficult. For instance, GDM is both an application
(display manager) and a user launching this application. Likewise for
most other display managers. Thus, there is a 1:1 mapping between
users and applications.
With seatd, from what I understand, there is no such mapping. However,
given your description, the following is unclear: Does alice need to be
in the seat group to run bash? To run sway? To run sway *only if not
having talked to greetd first*?
> > > > > + (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.
> > > ok field removed
> > Note ‘eq?’ groups here. In other words, you should be able to
> > take a
> > group (not just a group name) for the group field, sanitize the
> > field
> > so that it will always be a group, and then use that group in
> > seatd-
> > accounts (see the second option mentioned in
> > <79341a82bf9cd5fc6c2227255095f3fe2927dcbe.camel@ist.tugraz.at>).
> > If
> > for instance instead of seat, you wanted the video group, you
> > would
> > have to take the one from %base-groups, rather than creating a
> > new one.
> Sorry, but I'm not so proficient in english as you. I can only
> speculate on what is written here. And that reference does not
> say anything to me, even duck duck go gives single result, it is
> your message. Could you please be more specific here, and/or
> provide more useful hyperlink style references. Thanks in advance.
I'll explain it in terms of lisp:
(define seat1 (user-group (name "seat") (system #t))
(define seat2 (user-group (name "seat") (system #t))
(operating-system (groups (list seat1 seat1))) ; works, eq?
(operating-system (groups (list seat2 seat2))) ; works, eq?
(operating-system (groups (list seat1 seat2))) ; doesn't work
For field sanitizers, see define-record-type*.
Cheers
next prev parent reply other threads:[~2022-08-10 8:08 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
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 [this message]
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=feefa8add73babb6fb99636e1e676b1eae309c89.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).