linux-kernel - Re: Subject:[PATCH 1:1] boot paramer "root=" gets a list of devices

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4EEA10BC.3000906@zytor.com>
Date:	Thu, 15 Dec 2011 07:22:36 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	rbenyehuda@...z.com
CC:	"wad@...omium.org" <wad@...omium.org>,
	"kay.sievers@...y.org" <kay.sievers@...y.org>,
	Rasty Slutsker <RSlutsker@...z.com>,
	Lior Brafman <LBrafman@...z.com>, raziebe@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: Subject:[PATCH 1:1] boot paramer "root=" gets a list of devices

On 12/15/2011 07:19 AM, Raz Ben Yehuda wrote:
>>
>> To which point I have to ask, once again, at which point we stop putting
>> this stuff in the kernel to "bypass the need for initramfs"...
> because there are times where we cannot use initramfs. is this a problem
> with way i phrase or with with the whole idea ?
>

There are problems with the whole concept of "cannot use initramfs".  We 
allow the initramfs to be integrated with the kernel image for a reason, 
for example.

I'm obviously ranting on this in part to make people think about what 
they are doing, and partly to remind that the more complex the in-kernel 
root-mounting code get, the more it might be worth reconsidering klibc 
in the kernel build tree.

	-hpa

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/