public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: michael.opdenacker@bootlin.com
To: openembedded-core@lists.openembedded.org
Cc: docs@lists.yoctoproject.org,
	Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH] init-manager-none.inc: have no init manager
Date: Fri, 28 Apr 2023 11:06:02 +0200	[thread overview]
Message-ID: <20230428090602.82995-1-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <175A0DD84C89F64A.26969@lists.openembedded.org>

From: Michael Opdenacker <michael.opdenacker@bootlin.com>

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.

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
 meta/conf/distro/include/init-manager-none.inc | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/meta/conf/distro/include/init-manager-none.inc b/meta/conf/distro/include/init-manager-none.inc
index bbedf898f7..56d2b0f406 100644
--- a/meta/conf/distro/include/init-manager-none.inc
+++ b/meta/conf/distro/include/init-manager-none.inc
@@ -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 ??= ""
-- 
2.34.1



       reply	other threads:[~2023-04-28  9:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <175A0DD84C89F64A.26969@lists.openembedded.org>
2023-04-28  9:06 ` michael.opdenacker [this message]
2023-05-02 14:14   ` [OE-core] [PATCH] init-manager-none.inc: have no init manager Alexandre Belloni
2023-05-02 14:17     ` Michael Opdenacker
2023-05-02 14:18     ` [docs] " Richard Purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230428090602.82995-1-michael.opdenacker@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox