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 <[email protected]> wrote: > > > On 5/27/21 3:04 PM, [email protected] 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? > > > > Thanks, > > Priya > > > > > > > > > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#53690): https://lists.yoctoproject.org/g/yocto/message/53690 Mute This Topic: https://lists.yoctoproject.org/mt/83136294/21656 Mute #dunfell:https://lists.yoctoproject.org/g/yocto/mutehashtag/dunfell Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
