if I compile and deploy an apalis-tk1 LXDE image I find some startup services within systemd and others within init.d. The startup manager is set to default “cat /proc/1/comm” systemd.
So:
“systemctl” lists that syslog.service is not found/ inactive
init.d/dmesg.sh has not been started after boot.
a) Why are some scripts/ services deployed in both service folders?
b) Which syslog can/should be used?
c) Can I switch easily to the init.d sysvinit system?
d) Is there any possibility to use both startup systems?
The image.bb contains these definitions:
IMAGE_DEV_MANAGER = “udev”
IMAGE_INIT_MANAGER = “systemd”
IMAGE_INITSCRIPTS = " "
IMAGE_LOGIN_MANAGER = “busybox shadow”
signalling, that openembedded-core/meta/recipes-core/initscripts (sysvinit/init.d) won’t be used.
But in the rootfs.manifest initscripts 1.0 is drawn although not explicitely IMAGE_INSTALL(ed).
I now started to exchange to systemd: DISTRO_FEATURES = “… sysvinit …”, but this leads to more settings to be changed: Please ensure that your setting of VIRTUAL-RUNTIME_init_manager (systemd) matches the entries enabled in DISTRO_FEATURES