From: openembedded-core@lists.openembedded.org <openembedded-core@lists.openembedded.org> On Behalf Of Khem Raj via lists.openembedded.org
> The rcS script that busybox-init provides is able to run scripts that > are available as part of sysvinit, therefore its fine to keep sysvinit > distro feature enabled so that we can build complex systems with > busybox as init system. > > Signed-off-by: Khem Raj <raj.k...@gmail.com> > --- > meta/conf/distro/include/init-manager-mdev-busybox.inc | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/meta/conf/distro/include/init-manager-mdev-busybox.inc > b/meta/conf/distro/include/init-manager-mdev-busybox.inc > index 12091cba68c..a5a61bbe4d2 100644 > --- a/meta/conf/distro/include/init-manager-mdev-busybox.inc > +++ b/meta/conf/distro/include/init-manager-mdev-busybox.inc > @@ -1,5 +1,6 @@ > # enable mdev/busybox for init > -DISTRO_FEATURES_BACKFILL_CONSIDERED:append = " systemd sysvinit" > +DISTRO_FEATURES:append = " sysvinit" I don't think that this append is a good idea. I want a small, lean, controllable init system, not a complex one. This probably belongs to distro or to a new INIT_MANAGER type. > +DISTRO_FEATURES_BACKFILL_CONSIDERED:append = " systemd" > VIRTUAL-RUNTIME_dev_manager ??= "busybox-mdev" > VIRTUAL-RUNTIME_init_manager ??= "busybox" > VIRTUAL-RUNTIME_initscripts ??= "initscripts" > -- > 2.43.0
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#191126): https://lists.openembedded.org/g/openembedded-core/message/191126 Mute This Topic: https://lists.openembedded.org/mt/102757523/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
