In-Reply-To: <200410111229.02054.arekm@pld-linux.org>
References: <200410102315.i9ANF7OI019460@hacksaw.org> <047CCB21-1B66-11D9-96AD-000D9352858E@linuxmail.org> <200410111229.02054.arekm@pld-linux.org>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <6AADA244-1B7D-11D9-96AD-000D9352858E@linuxmail.org>
Content-Transfer-Encoding: 7bit
Cc: linux-kernel@vger.kernel.org
From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Subject: Re: udev: what's up with old /dev ?
Date: Mon, 11 Oct 2004 14:02:25 +0200
To: Arkadiusz Miskiewicz <arekm@pld-linux.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1137
Lines: 28

On Oct 11, 2004, at 12:29, Arkadiusz Miskiewicz wrote:

> On Monday 11 of October 2004 11:14, Felipe Alfaro Solana wrote:
>> On Oct 11, 2004, at 01:15, Hacksaw wrote:
>>>> The very first thing init does is open /dev/console, and if it 
>>>> doesn't
>>>> exist the entire boot hangs.
>>>
>>> This raises a question: Would it be a useful thing to make a modified
>>> init
>>> that could run udev before it does anything else?
>>
>> FC3t2 boots from an "initrd" image that, among other things, mounts a
>> tmpfs over "/dev" and creates "console", "null", "pts" and then
>> proceeds to load "init".
> ... and it ignores root= kernel cmdline option. rootfs is hardcoded in 
> initrd
> which is very ugly.

I haven't seen any hardcoded root filesystem reference in the INITRD 
image. Instead, I see "/dev/root" which is supposed to be exactly the 
root filesystem passed to the kernel via "root=".

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