linux-kernel - Re: [PATCH] docs: clarify rdinit precedence and correct ramdisk to initramfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250130100446.GA1162389@lichtman.org>
Date: Thu, 30 Jan 2025 10:04:46 +0000
From: Nir Lichtman <nir@...htman.org>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: corbet@....net, paulmck@...nel.org, akpm@...ux-foundation.org,
	rostedt@...dmis.org, Neeraj.Upadhyay@....com, mcanal@...lia.com,
	thuth@...hat.com, ardb@...nel.org, bp@...en8.de,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	rob@...dley.net
Subject: Re: [PATCH] docs: clarify rdinit precedence and correct ramdisk to
 initramfs

On Thu, Jan 30, 2025 at 10:52:02AM +0100, Greg KH wrote:
> On Thu, Jan 30, 2025 at 10:59:33AM +0200, Nir Lichtman wrote:
> > Problem: Current documentation regarding the init and rdinit params is
> > confusing,
> > The description of rdinit claims that it is related to ramdisks, even though
> > in practice
> > It only controls the init executable of the initramfs
> > (the deprecated ramdisk mechanism is initialized only after attempting to
> > load rdinit
> > or its default "/init")
> > Rob Landley's document from 2005 "Ramfs, rootfs and initramfs"
> > clarifies the distinction between initramfs and ramdisk.
> > Another confusing point is that the init param is ignored, in case rdinit or
> > "/init"
> > exist and are executable in the initramfs; the source code gives priority to
> > rdinit.
> > 
> 
> Odd line-wrapping, please fix :(
> 
[..]
> 
> Your patch is also line-wrapped and will not apply at all :(

Oops mistake, sorry about that, sending a fixed v2.

> 
> thanks,
> 
> greg k-h