>Hello,
>I'm currently running at 2.6.0-test1-mm2-O8 and I wanted to give devfs a
>shot. I recompiled the kernel with the following settings:
>CONFIG_DEVFS_FS=y
>CONFIG_DEVFS_MOUNT=y
># CONFIG_DEVFS_DEBUG is not set
>As I read through the documentation (btw, devfs=nomount is mentioned in
>configure help but not in Documentation/filesystems/devfs/boot-options)
>I got the understanding that this shouldn't make any difference to the
>system right? After booting with this kernel there were lots of proper
>devfs devices in my dmesg (host0/ide0... scsi0/...) however, the system
>didn't came up (couldn't mount rootfs). It didn't even work when I
>enabled CONFIG_DEVFS_MOUNT.
>I'm not sure whether this is a bug in mount/nomount of devfs or if it's
>somewhere my fault/setup (root on raid1, various lvm2 devices on raid1/0
>devices)
>Any help would be greatly appreciated.
You need to change your /etc/fstab to reflect the new devfs device names,
ex: "/dev/discs/disc0/part1" instead of "/dev/hda1". You can also use devfsd (or some alternative) to make synlinks to the older devices and retain permissions etc... Also, without devfsd you cannot expect module autoloading as modules can't be automatically loaded when theres no device requesting them (in this case the device simply doesn't exist until module is loaded)
-
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/
This archive was generated by hypermail 2b29 : Thu Jul 31 2003 - 22:00:26 EST