From: Nir Lichtman <nir@lichtman.org>
To: corbet@lwn.net, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Documentation: Fix confusing descriptions of rdinit and init
Date: Sun, 23 Nov 2025 09:08:38 +0200 [thread overview]
Message-ID: <aSKyeGTFNoGVo95O@nirs-laptop.local> (raw)
Problem: Documentation of init does not emphasize that it is only used
when initramfs failed to load and the legacy logic of direct root
partition mounting is started.
Documentation of rdinit uses the legacy term ramdisk even though
nowadays it controls the init process of initramfs.
Solution: Fix and modernize both.
Ref: init/main.c and the kernel doc article "Ramfs, rootfs and initramfs"
Signed-off-by: Nir Lichtman <nir@lichtman.org>
---
Documentation/admin-guide/kernel-parameters.txt | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index 6c42061ca..63170346c 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -2305,8 +2305,9 @@
init= [KNL]
Format: <full_path>
- Run specified binary instead of /sbin/init as init
- process.
+ Run specified binary instead of /sbin/init as init process
+ from root partition, used in case init was not found
+ in the initramfs.
initcall_debug [KNL] Trace initcalls as they are executed. Useful
for working out where the kernel is dying during
@@ -6194,7 +6195,7 @@
rdinit= [KNL]
Format: <full_path>
- Run specified binary instead of /init from the ramdisk,
+ Run specified binary instead of /init from the initramfs,
used for early userspace startup. See initrd.
rdrand= [X86,EARLY]
--
2.49.1
reply other threads:[~2025-11-23 7:14 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=aSKyeGTFNoGVo95O@nirs-laptop.local \
--to=nir@lichtman.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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