public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH V3 1/2] base-passwd: add clock group
Date: Mon, 20 Oct 2025 13:14:41 +0800	[thread overview]
Message-ID: <6d4ae9fd-b708-4b22-a170-68af462a7b39@windriver.com> (raw)
In-Reply-To: <CANNYZj8i4ksk_8kmDjswjA_pvQw-cCg_jOOCh47PYDu3TXw6Bw@mail.gmail.com>

On 10/18/25 02:22, Alexander Kanavin wrote:
> On Fri, 17 Oct 2025 at 04:56, Chen Qi via lists.openembedded.org
> <Qi.Chen=windriver.com@lists.openembedded.org> wrote:
>>> Why does this have to go here. Why can't you just update the
>>> GROUPADD_PARAM:${PN} in the systemd recipe to create the clock group:
>>>
>>> GROUPADD_PARAM:${PN} = "-r systemd-journal; -r clock;"
>>>
>>> That way it is only created if systemd is actually used.
>> I consider this clock similar to the 'wheel' and 'kvm' groups. 'wheel'
>> and 'kvm' groups are added here, so I put 'clock' group here.
>>
>>   From my understanding, such groups are likely to be used by other
>> applications (recipes). You can see this from the original commit:
>> https://github.com/systemd/systemd/commit/af96ccfc24bc4803078a46b4ef2cdeb
>>
>> It's possible that applications such as linuxptp will use this clock
>> group. What systemd (udev) does is to change the device's group to
>> 'clock'. This means applications using those devices could be put in
>> 'clock' group to be granted access.
> But how do classic binary distributions handle this? Can you research
> where e.g. Fedora or Debian create this group? We could probably
> follow that, and avoid having to carry an Inappropriate patch. Maybe
> base-passwd upstream already has a fix?
>
> Alex

Hi Alex,

I just checked the fedora:latest container. It also puts 'clock' group 
in a basic setup package, which, according to its description, is 
basically 'base-passwd + base-files' in Yocto.

See commands and results below:
"""
[root@607fbfbf12bb /]# grep clock /etc/group
clock:x:103:
[root@607fbfbf12bb /]# rpm -qf /etc/group
setup-2.15.0-13.fc42.noarch
[root@607fbfbf12bb /]# rpm -qi setup | grep -A 4 Summary
Summary     : A set of system configuration and setup files
Description :
The setup package contains a set of important system configuration and
setup files, such as passwd, group, and profile.
"""

I also checked base-passwd upstream and debian:latest container. 
base-passwd upstream does not have clock group: 
https://salsa.debian.org/debian/base-passwd/-/blob/master/group.master?ref_type=heads. 
And debian:latest is using systemd 257.8 so it does not have this 
'clock' group issue now.

I'll use gid 103 in patch V4 to sync with fedora (though not necessary).

Regards,
Qi



  reply	other threads:[~2025-10-20  5:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16  8:46 [OE-core][PATCH V3 1/2] base-passwd: add clock group Qi.Chen
2025-10-16  8:47 ` [OE-core][PATCH V3 2/2] systemd: upgrade from 257.8 to 258 Qi.Chen
2025-10-17 16:18   ` Mathieu Dubois-Briand
2025-10-18 13:49     ` Mathieu Dubois-Briand
2025-10-20  4:37       ` ChenQi
2025-10-22  3:28       ` ChenQi
2025-10-23  8:29         ` Mathieu Dubois-Briand
2025-10-23 13:49         ` Mathieu Dubois-Briand
2025-10-24  2:42           ` ChenQi
2025-10-27  5:07           ` ChenQi
2025-10-16  9:49 ` [OE-core][PATCH V3 1/2] base-passwd: add clock group Peter Kjellerstedt
2025-10-17  2:56   ` ChenQi
2025-10-17 18:22     ` Alexander Kanavin
2025-10-20  5:14       ` ChenQi [this message]
2025-10-20 11:59         ` Alexander Kanavin
2025-10-20 14:29           ` Peter Kjellerstedt

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=6d4ae9fd-b708-4b22-a170-68af462a7b39@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox