linux-kernel - RE: could not find filesystem /dev/root

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: <004001c70252$82702570$4b00a8c0@donald>
Date:	Tue, 7 Nov 2006 10:52:55 +0100
From:	"Paul Rolland" <rol@...917.net>
To:	"'Jan Engelhardt'" <jengelh@...ux01.gwdg.de>
Cc:	"'Marc Perkel'" <marc@...kel.com>,
	"'Chris Lalancette'" <clalance@...hat.com>,
	"'Rafael J. Wysocki'" <rjw@...k.pl>, <linux-kernel@...r.kernel.org>
Subject: RE: could not find filesystem /dev/root

Hello,

> The order in which disks are discovered, is basically
> (1) what module (let's take the "core kernel" as a module 
> too) is loaded first (core kernel always comes first)
> (2) running order of the __init functions in a specific module;
>     running order mostly defined by linking order

Yes... What is painful is that moving from a configuration with modules
to a configuration without modules, this can change. 

> >and resulted in drives changing devices :
> >FC5               Vanilla
> >/dev/sda   <--->  /dev/sdb
> >/dev/sdb   <--->  /dev/sdc
> >/dev/sdc   <--->  /dev/sda

> If you don't want udev, make an initramfs, build your disk driver as 
> modules, and load them in the order you want your disks numbered.
> 
> udev or initramfs, you ought to choose at least one.

Nope, you don't. I'm now using a kernel without modules for what's disk 
related, and unless people (read kernel developpers) change something 
in the init order, I'm now with a stable environment, without udev or
initramfs.

Paul

-
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/