I've been working with this problem over the weekend, and I have the
following facts to add to the mix.
(1) As far as I can tell, this is a problem with udev, not with 2.6.14
only. I tried to boot my machine using udev on 2.6.12, and ran into what
seems to be the same problem:
/sbin/init: 432 cannot create /dev/null
/sbin/init: 433 cannot open dev/null
Kernel-panic etc.
I view this as a migration problem from devfs to udev. If there's clear
instructions on how to accomplish a migration, I don't know what they are.
(2) I was able to install 2.6.14 *without* having udev installed! Since
2.6.14 seems to rely on udev and yaird, I believe udev should be a
depedency of 2.6.14.
(3) I thought that perhaps the problem was DELAY=10 in my mkinitrd.conf;
but I tried building 2.6.12 using DELAY=0, and I still bomb out.
I frankly am perplexed by this problem. My /dev is completely cluttered
with everything that devfs created, I have a /dev/.static directory with
console, null, and zero present, yet I can't seem to boot under udev. I
wonder if the problem is that devfs is attempting to come up before udev?
--
Moshe Yudkowsky
Disaggregate
2952 W Fargo
Chicago, IL 60645 USA
www.Disaggregate.com
www.PebbleAndAvalanche.com
[EMAIL PROTECTED]
+1 773 764 8727
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
