From: Markus Pargmann <mpa@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Markus Pargmann <mpa@pengutronix.de>
Subject: [ptxdist] [PATCH] rootfs: Add Option to install /sbin/init as /init
Date: Wed, 11 Nov 2015 11:07:56 +0100 [thread overview]
Message-ID: <1447236476-29551-1-git-send-email-mpa@pengutronix.de> (raw)
The kernel searches in initramfs for an executable /init file. So if we
want to use initramfs as rootfs it is convenient to have a link from
/init to /sbin/init.
Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
---
rules/rootfs.in | 17 ++++++++++++++++-
rules/rootfs.make | 8 ++++++++
2 files changed, 24 insertions(+), 1 deletion(-)
diff --git a/rules/rootfs.in b/rules/rootfs.in
index 80a730594892..102282b4c339 100644
--- a/rules/rootfs.in
+++ b/rules/rootfs.in
@@ -440,5 +440,20 @@ config ROOTFS_SERVICES
If enabled, it installs the "./projectroot/etc/services" file if
present, else a generic one from the ptxdist directory.
-endmenu
+config ROOTFS_INIT
+ bool
+ prompt "/init"
+ default y
+ help
+ Create a symlink from /init to /sbin/init. This is useful for
+ initramfs for example in which /init is executed by default.
+config ROOTFS_INIT_BIN
+ depends on ROOTFS_INIT
+ bool
+ prompt "Install /init binary"
+ default n
+ help
+ Install the /init binary instead of a symlink to /sbin/init.
+
+endmenu
diff --git a/rules/rootfs.make b/rules/rootfs.make
index 65cf0d126336..35568567fd82 100644
--- a/rules/rootfs.make
+++ b/rules/rootfs.make
@@ -240,6 +240,14 @@ ifdef PTXCONF_ROOTFS_SERVICES
@$(call install_alternative, rootfs, 0, 0, 0644, /etc/services)
endif
+ifdef PTXCONF_ROOTFS_INIT
+ ifdef PTXCONF_ROOTFS_INIT_BIN
+ @$(call install_alternative, rootfs, 0, 0, 0755, /init)
+ else
+ @$(call install_link, rootfs, /sbin/init, /init)
+ endif
+endif
+
@$(call install_finish, rootfs)
@$(call touch)
--
2.6.1
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
reply other threads:[~2015-11-11 10:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1447236476-29551-1-git-send-email-mpa@pengutronix.de \
--to=mpa@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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