> i have one machine that i passed to the new kernel that can't boot anymore
> since all seem to indicate that the proc is mounted on /dev hiding thus all
> devices and making the boot procedure impossible....
>
> is this something known, and is there any counter-mesure to it?
This is not /proc, this the new filesystem called devfs. Just pass
"devfs=nomount" as a boot option and it won't mount on /dev by default.
The above on its own is not enough, of course you should read
Documentation/filesystems/devfs/README. But it will at least get your
system back... Then you should convert your /etc/fstab,
/etc/rc.d/rc.sysinit, util-linux,console-tools, mouseconfig, XFree86 and
probably a couple more (escapes my memory, I should have the patches lying
somewhere as I did some of the hacks for those when I needed a
"pure-devfs-no-compatibility-system") and you should be ok.
Or, you can run devfsd or create a few symlinks manually on boot -
basically nothing much to worry about (despite all the shouting arguments
here saying that devfs breaks everything - it doesn't).
Regards,
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:22 EST