Reply-To: <rol@as2917.net>
From: "Paul Rolland" <rol@as2917.net>
To: "'Jan Engelhardt'" <jengelh@linux01.gwdg.de>
Cc: "'Marc Perkel'" <marc@perkel.com>,
       "'Chris Lalancette'" <clalance@redhat.com>,
       "'Rafael J. Wysocki'" <rjw@sisk.pl>, <linux-kernel@vger.kernel.org>
Subject: RE: could not find filesystem /dev/root
Date: Tue, 7 Nov 2006 10:52:55 +0100
Organization: AS2917.net
Message-ID: <004001c70252$82702570$4b00a8c0@donald>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.LNX.4.61.0611071013420.11192@yvahk01.tjqt.qr>
Thread-Index: AccCTeH044QjMYmcTgqRrJ9Fip1lBgABBaGw
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1267
Lines: 34

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/