On Mon, Nov 13, 2017 at 12:59 PM, Andre McCurdy <[email protected]> wrote: > On Mon, Nov 13, 2017 at 12:26 PM, Patrick Ohly <[email protected]> wrote: >> On Mon, 2017-11-13 at 12:18 -0800, Andre McCurdy wrote: >>> On Mon, Nov 13, 2017 at 6:48 AM, Patrick Ohly <[email protected] >>> > wrote: >>> > On Thu, 2017-11-09 at 21:54 -0800, Andre McCurdy wrote: >>> > > The default systemd-tmpfiles config file expects to be able to >>> > > create >>> > > files etc belonging to the wheel system group. Currently the >>> > > wheel >>> > > group is created at run time by systemd-sysusers, but that >>> > > doesn't >>> > > happen if systemd-sysusers is disabled (as it currently is by >>> > > default >>> > > when building with musl libc). >>> > >>> > Isn't this something that the systemd_create_users rootfs >>> > postprocess >>> > command in rootfs-postcommands.bbclass already takes care of? >>> >>> systemd_create_users() does a build time pass over the >>> systemd-sysusers config files, but those files are not installed if >>> systemd is configured without sysusers support. >> >> I didn't know that this is optional. To me it sounds like an invalid >> (or let's say, unexpected) configuration to install tmpfiles config >> files but not the sysusers files, because as you said, the tmpfiles may >> depend on the sysusers. > > In the current recipe, there's no control of tmpfiles (so it will > always be enabled) and sysusers is controlled by PACKAGECONFIG > (enabled by default - but only when building with glibc), so the > recipe does allow that combination. > >> Anyway, I just wanted to know because I was wondering whether it is >> really necessary to duplicate the user creation information in the >> systemd recipe. >>
Ping. Ross, it looks like you've started to stage the later systemd + musl cleanups in mut. This fix is needed too. -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
