From: "Puustinen, Ismo" <ismo.puustinen@intel.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"stephano.cetola@linux.intel.com"
<stephano.cetola@linux.intel.com>
Subject: Re: [PATCH v2 0/2] Create systemd users at build time
Date: Wed, 11 May 2016 10:46:38 +0000 [thread overview]
Message-ID: <1462963597.11059.13.camel@intel.com> (raw)
In-Reply-To: <1462837346-27095-1-git-send-email-stephano.cetola@linux.intel.com>
On Mon, 2016-05-09 at 16:42 -0700, Stephano Cetola wrote:
> Systemd has a config option sysusers which creates any users or
> groups that
> systemd needs on first boot. There is a rootfs-postcommand that
> creates these
> users in case the filesystem is readonly, however it does not take
> into
> account any staicids that the user may have set.
>
> By adding these users at build time, we allow a check for staticids,
> which would
> otherwise have been skipped.
I think this is a valuable feature. However, have you considered adding
the "m" and "r" options too? I think that at least "m" would be
worthwhile to implement, since it's important to be able to add users
to different groups for privilege management.
Ismo
next prev parent reply other threads:[~2016-05-11 10:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 23:42 [PATCH v2 0/2] Create systemd users at build time Stephano Cetola
2016-05-09 23:42 ` [PATCH v2 1/2] systemd: add sysusers config option to defaults Stephano Cetola
2016-05-09 23:50 ` Khem Raj
2016-05-10 0:24 ` Stephano Cetola
2016-05-09 23:42 ` [PATCH v2 2/2] systemd: add users/groups at build rather than runtime Stephano Cetola
2016-05-09 23:49 ` Khem Raj
2016-05-10 0:55 ` Stephano Cetola
2016-05-10 0:58 ` Khem Raj
2016-05-11 10:46 ` Puustinen, Ismo [this message]
2016-05-11 19:04 ` [PATCH v2 0/2] Create systemd users at build time Stephano Cetola
2016-05-12 11:17 ` Puustinen, Ismo
2016-05-12 15:30 ` Stephano Cetola
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=1462963597.11059.13.camel@intel.com \
--to=ismo.puustinen@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=stephano.cetola@linux.intel.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.