When relying on useradd-staticids, this commit [1] made the problems that
this [2] bug causes, much worse. Prior to that commit we could predict with
surprising accuracy what the UID and GID would be for the very small number
of systemd-* accounts that were created (or simply patch the expected
UID/GID values in, but that never became necessary). After that commit, a
bunch of system accounts and groups get created with the wrong UID and/or
GID.

I suppose this is an opportunity to implement BZ9789. But since this issue
is so old it either means it was forgotten, or it is really hard in some
non-obvious way. Is there any insight available into which it is?

The solution seems pretty straight forward, so that pretty much guarantees
I am missing something important. In the systemd_create_users function
inherit extrausers, set the appropriate variables, call set_user_group
directly, and then remove set_user_group from ROOTFS_POSTPROCESS_COMMAND.

So where did I go wrong there?

Also, does it make sense to return from systemd_create_users early if
read-only-rootfs is *NOT* in IMAGE_FEATURES?

Thank you,

..Ch:W..

P.S. I think there is also a legitimate bug in systemd_create_users. I
noticed a few situations where it was trying to add a non-standard home
directory to the useradd command, but it was missing the --home-dir flag,
so the useradd command silently broke and did not fail the build.

1.
https://git.openembedded.org/openembedded-core/commit/?id=a94e622f222253c6646f1a1157f918d8aa586866
2. https://bugzilla.yoctoproject.org/show_bug.cgi?id=9789

-- 
*"Perfection must be reached by degrees; she requires the slow hand of
time." - Voltaire*
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161387): 
https://lists.openembedded.org/g/openembedded-core/message/161387
Mute This Topic: https://lists.openembedded.org/mt/88922422/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to