All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: TIAN Yuanhao <tianyuanhao3@163.com>
Cc: Norbert Lange <nolange79@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/systemd: add the missing sgx group
Date: Sun, 24 Apr 2022 16:50:21 +0200	[thread overview]
Message-ID: <20220424145021.GV2730@scaer> (raw)
In-Reply-To: <0fd2d0f7-d067-0f65-23dd-68aff1e61d94@163.com>

Yuanhao, All,

On 2022-04-21 16:55 -0700, TIAN Yuanhao spake thusly:
> On 4/21/22 12:16, Yann E. MORIN wrote:
> >On 2022-04-20 06:55 -0700, TIAN Yuanhao spake thusly:
> >>systemd-udevd needs this group:
> >>   /usr/lib/udev/rules.d/50-udev-default.rules:43 Unknown group 'sgx', ignoring
[--SNIP--]
> >>diff --git a/package/systemd/systemd.mk b/package/systemd/systemd.mk
> >>index b07fac27d4..44185a35a0 100644
> >>--- a/package/systemd/systemd.mk
> >>+++ b/package/systemd/systemd.mk
> >>@@ -603,6 +603,7 @@ endef
> >>  define SYSTEMD_USERS
> >>  	# udev user groups
> >>+	- - sgx -1 * - - - SGX device nodes
> >This should have been in the udev virtual package, as all the
> >udev-related users and groups have been moved there to be common between
> >systemd-udevd and the stand-alone eudev, in commit d648d81dd581
> >(packages/{eudev, systemd}: move common users to package/udev).
> I did notice the common rules in the udev virtual package. However "sgx"
> only appears in systemd but not eudev.

OK, my bad. Can you send a patch that moves it back to systemd, please?

> Besides, I found that the "render"
> group in systemd should be "video" in eudev.

This is going to be concerning if the same device nodes have different
groups assigned to them by the two different udev implementations...

In systemd, the renderD* nodes have always been assigned to group
'render', since commit 4e15a7343cb3 (udev-rules: Permission changes for
/dev/dri/renderD*), committed 2017-11-08.

In eudev, renderD* nodes were also assigned to the 'render' group in
commit bb070c154e70 (rules: update), committed 2018-02-20.

But then, in eudev, that was changed with commit a8ffcd1b985f
(rules/50-udev-default.rules: fix issue 160), where they were then
assigned to the 'video' group.

There is not much that is interesting in issue 160, except for some
people reporting issues on distros where the 'render' group does not
exist (along with a bit of the usual whining about systemd).

So, I'm not sure how we should go in that case... Indeed, if we have
packages which want to declare users that belong to the appropriate
group to be able to use the render nodes, then they'd have to know
whether running with systemd or eudev, which was initially the reason to
have a virtual package to abstract that, and have the groups defined in
that virtual package...

Sigh...

But in the end, then yes, 'render' and 'video' should be moved out of
the virtual package and into systemd and eudev, respectively. Can you do
that, please?

Regards,
Yann E. MORIN.

> Regards,
> TIAN Yuanhao
> >
> >Regards,
> >Yann E. MORIN.
> >
> >>  	# systemd user groups
> >>  	- - systemd-journal -1 * - - - Journal
> >>  	$(SYSTEMD_REMOTE_USER)
> >>-- 
> >>2.25.1
> >>
> >>_______________________________________________
> >>buildroot mailing list
> >>buildroot@buildroot.org
> >>https://lists.buildroot.org/mailman/listinfo/buildroot
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-04-24 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20 13:55 [Buildroot] [PATCH] package/systemd: add the missing sgx group TIAN Yuanhao
2022-04-21 19:16 ` Yann E. MORIN
2022-04-21 23:55   ` TIAN Yuanhao
2022-04-24 14:50     ` Yann E. MORIN [this message]
2022-05-24  8:19 ` Peter Korsgaard

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220424145021.GV2730@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=nolange79@gmail.com \
    --cc=tianyuanhao3@163.com \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.