[poky] systemd and sysvinit enabled in DISTRO_FEATURES

[Hector Almeida]

Hi Ross,


thanks for answering.


On my main image, under /etc/init.d I have:

alsa-state     bluetooth      dbus-1         functions hwclock.sh     
networking     syslog
avahi-daemon   connman        dropbear       fuse modutils.sh    
ntpd           run-postinsts  systemd-udevd


For example, in connman's recipe, the 'connman' sysvinit script is 
installed if 'DISTRO_FEATURES' contains 'sysvinit'. But then, is there 
any other procedure that would delete this file from an image the 
chooses systemd as init manager?


Also, on packagroup-core-boot, if 'DISTRO_FEATURES' contains 'sysvinit', 
the following additional packages that contains sysvinit scripts are 
installed: 'init-ifupdown' and 'modutils-initscripts'. I don't 
understand the sense of this, since in the Yocto documentation I 
attached on the previous mail, it says that the main image will use 
packagroup-core-boot and the rescue image should not use it. So, I will 
get init-ifupdown and modutils-initscripts on the main image that uses 
systemd, and I should't use packagegroup-core-boot on the rescue image 
that is the one that really needs those packages (of course I can 
manually add this two packages to my rescue image, I'm just trying to 
under how all this should work).


Hector


On 14/1/19 21:35, Burton, Ross wrote:
> On Tue, 15 Jan 2019 at 00:19, Hector Almeida <hector at ikatu.com 
> <mailto:hector at ikatu.com>> wrote:
>
>     But I end up with the /etc/init.d folder with a lot of sysvinit
>     scripts in my main image. Also I have some systemd files on my
>     rescue image under /etc/systemd.
>
>
> What files are in each place?  It's entirely possible that you're 
> using recipes that ship just one or the other, or recipes that don't 
> correctly use the classes.
>
> Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/poky/attachments/20190114/a4f7c34c/attachment-0001.html>