followup to previous post ... with master oe-core, i did:
* MACHINE = qemuarm64
* core-image-minimal
with only customization:
INIT_MANAGER = "systemd"
the end result was a bootable QEMU image which had the executable
/sbin/nologin, but a number of systemd-related user accounts with
login shell "/bin/nologin" (which does not exist in the image).
the systemd accounts are clearly created as a result of this from
the systemd recipe file (which hardcodes the selection of
/bin/nologin):
USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG',
'networkd', '--system -d / -M --shell /bin/nologin systemd-network;',
'', d)}"
USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG',
'resolved', '--system -d / -M --shell /bin/nologin systemd-resolve;',
'', d)}"
USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG',
'timesyncd', '--system -d / -M --shell /bin/nologin
systemd-timesync;', '', d)}"
is this a bug? how does one properly make this consistent?
rday
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#137436):
https://lists.openembedded.org/g/openembedded-core/message/137436
Mute This Topic: https://lists.openembedded.org/mt/73228776/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
