linux-kernel - Re: boot device order troubleshooting without an initrd

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: <20100420051716.GB2075@ucw.cz>
Date:	Tue, 20 Apr 2010 07:17:16 +0200
From:	Pavel Machek <pavel@....cz>
To:	skitching@...che.org
Cc:	jkt@...too.org, linux-kernel@...r.kernel.org
Subject: Re: boot device order troubleshooting without an initrd

On Mon 2010-04-19 22:20:23, skitching@...che.org wrote:
> As it happens, I've been looking into this issue recently.
> [Warning: kernel newbie speaking!]
> 
> Without an initrd, the options for the root= kernel parameters are only those supported in init/do_mount.c:
>   1.   root=MAJOR:MINOR
>   2.   root=integer   where integer is MAJOR<<n + minor
>   3    root=/dev/xxx
> (well, apart fron "mtd" and "ubi" options).

And nfs?

> Unfortunately, all of these options are sensitive to hardware changes, ie device enumeration order. So I 
> think that right now the answer to your question is: no, you can't get what you want without an initrd.
> 
> And I doubt that changes to the linux device-enumeration code "to be consistent with the BIOS" would be accepted.
>

If it is clean enough... why not?

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/