Tried setting INIT_MANAGER = " sysvinit" in build/conf/local.conf
Is it INIT_MANAGER = " sysvinit" , or INIT_MANAGER = "sysvinit" (no blank at the beginning)?
Thank you, Zee _______
On Fri, May 28, 2021 at 1:47 PM Swapna Nannapaneni <sayinswapna@...> wrote:
Thanks Robert and Raj!!
I am using Yocto 3.1 Dunfell release.
You are right about the .bbappend file. Changed the name in the overlay to new-ver.bbappend and no longer see the warning.
Tried setting INIT_MANAGER = " sysvinit" in build/conf/local.conf but looks like generated rootfs has init file pointing to init -> ../lib/systemd/systemd
Priya.
On Thu, May 27, 2021 at 7:28 PM Khem Raj <raj.khem@...> wrote:
On 5/27/21 3:04 PM, sayinswapna@... wrote:
Hello Yocto team:
I just started with yocto and would like to know the process for switching the init manager from systemd to sysvinit.
I tried this options in config file VIRTUAL-RUNTIME_init_manager = "busybox" PREFERRED_PROVIDER_udev = "sysvinit" PREFERRED_PROVIDER_udev-utils = "sysvinit" DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit" DEFAULT_DISTRO_FEATURES += " sysvinit"
I see a warning when building my machine:
No recipe for target: /recipes-core/sysvinit/sysvinit_2.88dsf.bbappend
Please find out which layer is adding this bbappend you could use
bitbake-layers show-appends sysvinit
It seems recipe version is newer perhaps and the bbappend is still made for older recipe, these things happen when you mix release branches for different layers.
When I run this build on my target it still shows me systemd init manager...
Not sure if I am missing any options. Could you please let me know if there are any pointers I can refer to?
