openembedded-core.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Louis Rannou <lrannou@baylibre.com>,
	tgamblin@baylibre.com,
	 "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [RFC] incorrect parsing of sysusers.d in rootfs generation
Date: Thu, 08 Jun 2023 10:19:52 +0100	[thread overview]
Message-ID: <a5e311b0545dc84f64d985ffcbd595bff2f2a2ff.camel@linuxfoundation.org> (raw)
In-Reply-To: <08e9842b-0288-92c9-6327-a82e37f4af99@baylibre.com>

On Wed, 2023-06-07 at 17:16 +0200, Louis Rannou wrote:
> Hello again,
> 
> a python solution could be one below.
> 
> Also, I found that most of users/groups defined there are redundant as 
> they already exist (such as root). I guess they are defined from 
> base-passwd. I am not sure which recipe (base-passwd or systemd) should 
> have the precedence on this. If it's base-passwd, perhaps this 
> postcommand should check first if the user does already exist.

I'd say base-passwd should likely be the winner but we should probably
error if there is a conflict between what sysusers.d and base-passwd
are defining.

Cheers,

Richard


  reply	other threads:[~2023-06-08  9:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05 15:55 [RFC] incorrect parsing of sysusers.d in rootfs generation Louis Rannou
2023-06-07 15:16 ` Louis Rannou
2023-06-08  9:19   ` Richard Purdie [this message]
2023-06-08 10:28     ` [OE-core] " Louis Rannou
2023-06-08 10:36       ` Richard Purdie
2023-06-08 11:56         ` Louis Rannou
2023-06-09 11:06           ` Louis Rannou

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=a5e311b0545dc84f64d985ffcbd595bff2f2a2ff.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=lrannou@baylibre.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=tgamblin@baylibre.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;
as well as URLs for NNTP newsgroup(s).