From: "Khem Raj" <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Khem Raj <raj.khem@gmail.com>, Sinan Kaya <okaya@kernel.org>
Subject: [PATCH 1/3] rcS: Define identifier for init system used
Date: Fri, 18 Dec 2020 18:23:41 -0800 [thread overview]
Message-ID: <20201219022343.3362531-1-raj.khem@gmail.com> (raw)
This will help in defining init system specific portions of initscripts
which are shared
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Sinan Kaya <okaya@kernel.org>
---
meta/recipes-core/busybox/files/rcS.default | 3 ++-
meta/recipes-core/sysvinit/sysvinit/rcS-default | 3 +++
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-core/busybox/files/rcS.default b/meta/recipes-core/busybox/files/rcS.default
index 262cad7d2a..66513daf2d 100644
--- a/meta/recipes-core/busybox/files/rcS.default
+++ b/meta/recipes-core/busybox/files/rcS.default
@@ -1 +1,2 @@
-# SULOGIN = "yes"
+# Indicate init system type
+INIT_SYSTEM=busybox
diff --git a/meta/recipes-core/sysvinit/sysvinit/rcS-default b/meta/recipes-core/sysvinit/sysvinit/rcS-default
index 709cdf6ec5..e608a77c75 100644
--- a/meta/recipes-core/sysvinit/sysvinit/rcS-default
+++ b/meta/recipes-core/sysvinit/sysvinit/rcS-default
@@ -27,3 +27,6 @@ VOLATILE_ENABLE_CACHE=yes
# Setting ROOTFS_READ_ONLY to yes and rebooting will give you a read-only rootfs.
# Normally you should not change this value.
ROOTFS_READ_ONLY=no
+# rcS is also used when using busybox init and shares initscripts, some initscripts
+# need to have specific behavior depending on init system
+INIT_SYSTEM=sysvinit
--
2.29.2
next reply other threads:[~2020-12-19 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 2:23 Khem Raj [this message]
2020-12-19 2:23 ` [PATCH v2 2/3] initscripts: Use initctl on sysvinit only Khem Raj
2020-12-19 2:23 ` [PATCH 3/3] busybox: Sync rcS.default with sysvinit Khem Raj
2020-12-19 2:52 ` [PATCH 1/3] rcS: Define identifier for init system used Sinan Kaya
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=20201219022343.3362531-1-raj.khem@gmail.com \
--to=raj.khem@gmail.com \
--cc=okaya@kernel.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