mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Artur Wiebe via ptxdist <ptxdist@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Artur Wiebe <artur@4wiebe.de>
Subject: [ptxdist] [PATCH] usr-rootfs: always enable, decouple from initmethod
Date: Sat, 28 Mar 2026 17:19:43 +0100	[thread overview]
Message-ID: <20260328161943.966987-1-artur@4wiebe.de> (raw)

usr-rootfs installs the /usr merge symlinks (/bin → usr/bin,
/sbin → usr/sbin, /lib → usr/lib). These are required for any
dynamically linked binary to run, as the dynamic linker is looked
up via /lib64 → usr/lib.

Previously usr-rootfs was pulled in via "select USR_ROOTFS" in
initmethod. This broke minimal initramfs setups where /init is a
plain shell script and INITMETHOD is disabled: without the symlinks,
even busybox fails to start because the dynamic linker cannot be
found.

The UsrMerge layout is unconditionally needed on any target image,
so make USR_ROOTFS a bool with default y and remove the dependency
from initmethod.

Signed-off-by: Artur Wiebe <artur@4wiebe.de>
---
 rules/initmethod.in | 1 -
 rules/usr-rootfs.in | 3 ++-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/rules/initmethod.in b/rules/initmethod.in
index 6bf67d01c..cad86e6b7 100644
--- a/rules/initmethod.in
+++ b/rules/initmethod.in
@@ -2,7 +2,6 @@
 
 menuconfig INITMETHOD
 	bool  "init                          "
-	select USR_ROOTFS
 	default y
 	help
 	  Choose the system startup init method here
diff --git a/rules/usr-rootfs.in b/rules/usr-rootfs.in
index 8190c62d1..f8377ad37 100644
--- a/rules/usr-rootfs.in
+++ b/rules/usr-rootfs.in
@@ -1,5 +1,6 @@
 ## SECTION=rootfs
 
 config USR_ROOTFS
-	tristate
+	bool
+	default y
 	select BASE
-- 
2.53.0




                 reply	other threads:[~2026-03-28 16:20 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=20260328161943.966987-1-artur@4wiebe.de \
    --to=ptxdist@pengutronix.de \
    --cc=artur@4wiebe.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