4420 2013-04-25 15:32:35 +0000 core-image-sato with systemd only has psplash sysvinit script left - decide what to do with psplash 2020-05-14 08:16:37 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 1.4 All Multiple RESOLVED FIXED Medium enhancement Future 1 ross.burton unassigned bluelightning holger joshuagloe liezhi.yang meta.mr.watcher meta.watcher Qi.Chen radu.moisan randy.macleod richard.purdie ross.burton sgw --- --- No (bug/feature does not impact docs) oldest_to_newest 32653 0 ross.burton 2013-04-25 15:32:35 +0000 A pure-systemd build of core-image-sato should result in no sysvinit scripts being installed. meta-systemd is an obvious source of patches but these will need to be carefully reviewed. 33069 1 ross.burton 2013-05-13 15:49:08 +0000 Radu, can you take part 1 of this, the scoping? To get the list of recipes that need towk we can list all recipes that inherit update-rcd but don't inherit systemd. Then we can see what we can port from meta-systemd and what needs rewriting. 33082 2 radu.moisan 2013-05-14 10:10:55 +0000 yes, will compile a list asap 33094 3 radu.moisan 2013-05-15 08:58:32 +0000 I found the following, although I didn't go into each recipe in particular to check is systemd enabling makes sense. We need to enable systemd in (as grep'd for update-rc.d): acpid alsa-state apmd keymaps usbinit v86d ?? portmap init-ifupdown tcf-agent xserver-nodm-init modutils-initscripts ?? oprofileui-server Found some recipe that inherit systemd but not update-rc.d avahi wpa-supplicant util-linux Some recipes that I already have on poky-contrib (need rebasing/adjusting) xserver-nodm-init lighttpd cronie dropbear openssh dhcp keymaps 40261 4 holger 2014-02-10 07:54:14 +0000 http://cgit.openembedded.org/openembedded-core/commit/?id=5d90c5ebdb899b2951c97a94ff57867c1e491c15 Has this change been tested with online update? What happens if someone is doing opkg upgrade through a SSH connection and dropbear will be updated? Also http://cgit.openembedded.org/openembedded-core/commit/meta/recipes-core/dropbear?id=16b57e352f5844f301cc6c7ea4f87bf750c11d67 doesn't seem to be done inside the dropbearkeys.service 44973 5 Qi.Chen 2014-08-06 07:34:50 +0000 Two packages in OE still have the problem, v86d and alsa-state. //Chen Qi 44974 6 Qi.Chen 2014-08-06 07:38:00 +0000 The /etc/init.d/psplash.sh problem is related to Bug#4339 and should be solved there. 46913 7 Qi.Chen 2014-11-11 07:03:11 +0000 psplash is a blocker issue. //Chen Qi 47204 8 bluelightning 2014-11-26 12:09:44 +0000 FYI, there are now only two bbappends in meta-systemd left that have anything substantial in them - bluez4 and dhcp. We've already taken most things from the dhcp bbappend, but what's left is the dhclient service file (it may be questionable as to whether that's really needed though). http://cgit.openembedded.org/meta-openembedded/tree/meta-systemd/oe-core/recipes-connectivity/bluez http://cgit.openembedded.org/meta-openembedded/tree/meta-systemd/oe-core/recipes-connectivity/dhcp 64168 9 ross.burton 2016-07-19 16:22:54 +0000 Chen, have you analysed core-image-sato recently? 64254 10 Qi.Chen 2016-07-21 02:28:56 +0000 (In reply to comment #9) > Chen, have you analysed core-image-sato recently? Yes. The situation hasn't changed for a long time. The only script that's in /etc/init.d is psplash.sh. Someone sent out related patches about adding psplash services for systemd, but it seems that's not accepted. And then, if I recall correctly, someone adds plymouth in meta-oe, but it's not in oe-core. My question is, should we insist on psplash for sato images in OE, or we use plymouth when systemd is the init manager? Regards, Chen Qi 87193 11 richard.purdie 2020-05-14 08:16:37 +0000 http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=9ae26cfeea354039c1bdb42fb7289be55115681d