init-manager-none.inc: have no init manager
PATCH 1/1 init-manager-none.inc: have no init manager
In reply to a message not in the archiveFrom: Michael Opdenacker <[email protected]>
This fixes the issue that setting INIT_MANAGER to "none" produces a system with sysvinit.
As the name suggests, this produces a system without an init manager (no systemd, no sysvinit, no BusyBox init, no /etc/inittab). There isn't any login manager either. The kernel just starts /bin/sh in the console.
--- meta/conf/distro/include/init-manager-none.inc | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
meta/conf/distro/include/init-manager-none.inc +4 -3
@@ -1,3 +1,4 @@ -VIRTUAL-RUNTIME_init_manager ??= "sysvinit" -VIRTUAL-RUNTIME_initscripts ??= "initscripts" -VIRTUAL-RUNTIME_login_manager ??= "busybox" +DISTRO_FEATURES_BACKFILL_CONSIDERED:append = " systemd sysvinit" +VIRTUAL-RUNTIME_init_manager ??= "" +VIRTUAL-RUNTIME_initscripts ??= "" +VIRTUAL-RUNTIME_login_manager ??= ""
Signature · 1 line
2.34.1
Hello,
This causes the following error:
https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/7035/steps/12/logs/stdio
This is the expected behaviour of the patch but doesn't fit with what this particular build (qemuarm-oecore) is testing as we can't run testimage without an init. I'm wondering what should be the proper course of action here.
Quoted 40 lines · Michael Opdenacker via lists.openembedded.org
From: Michael Opdenacker <[email protected]>
This fixes the issue that setting
INIT_MANAGERto "none" produces a system with sysvinit.As the name suggests, this produces a system without an init manager (no systemd, no sysvinit, no BusyBox init, no
/etc/inittab). There isn't any login manager either. The kernel just starts/bin/shin the console.Signed-off-by Michael Opdenacker <[email protected]>--- meta/conf/distro/include/init-manager-none.inc | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)meta/conf/distro/include/init-manager-none.inc +4
-3@@ -1,3 +1,4 @@ -VIRTUAL-RUNTIME_init_manager ??= "sysvinit" -VIRTUAL-RUNTIME_initscripts ??= "initscripts" -VIRTUAL-RUNTIME_login_manager ??= "busybox" +DISTRO_FEATURES_BACKFILL_CONSIDERED:append = " systemd sysvinit" +VIRTUAL-RUNTIME_init_manager ??= "" +VIRTUAL-RUNTIME_initscripts ??= "" +VIRTUAL-RUNTIME_login_manager ??= ""Signature · 11 lines
2.34.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#180524): https://lists.openembedded.org/g/openembedded-core/message/180524 Mute This Topic: https://lists.openembedded.org/mt/98554799/3617179 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
Signature · 3 lines
Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Hi Alex,
Quoted 10 lines · Alexandre Belloni
Hello,
This causes the following error:
https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/7035/steps/12/logs/stdio
This is the expected behaviour of the patch but doesn't fit with what this particular build (qemuarm-oecore) is testing as we can't run testimage without an init. I'm wondering what should be the proper course of action here.
Thanks for the report!
Maybe another option is to remove the "none" option, as someone also suggested, as it is currently identical to the "sysvinit" option.
Any further thoughts?
Thanks again
Michael.
Signature · 3 lines
Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Quoted 11 lines · Alexandre Belloni via lists.yoctoproject.org
Hello,
This causes the following error:
https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/7035/steps/12/logs/stdio
This is the expected behaviour of the patch but doesn't fit with what this particular build (qemuarm-oecore) is testing as we can't run testimage without an init. I'm wondering what should be the proper course of action here.
INIT_MANAGER didn't used to be a variable and therefore could in theory be unset. The "none" configuration was designed to cause the system to fall back to the original behaviour. OE-Core's "nodistro" uses the fallback.
We could decide just to require this variable to be set to something but this could potentially conflict with people setting up their init system "manually" within their own distro.
It is a bit tricky to know what to do in situations like these. INIT_MANAGER was added to try and help people avoid needing to repeat certain config fragments.
Cheers,
Richard