The section of the devfs documentation which discusses the ability to
run a devfs-enabled kernel without devfs mounted is possibly confusing.
Hopefully this patch will make it easier to understand. It's against
2.4.20-pre3 but it applies to 2.4.19 and 2.5.31 as well.
For 2.4, please apply or explain any objections. If it's applied for
2.4, it would be good to apply it for 2.5 as well, although it might be
moot if devfs is killed during 2.5.
-Barry K. Nathan <[email protected]>
diff -ruN linux-2.4.20-pre3/Documentation/filesystems/devfs/README linux-2.4.20-pre3-bkn1/Documentation/filesystems/devfs/README
--- linux-2.4.20-pre3/Documentation/filesystems/devfs/README Thu May 16 01:58:33 2002
+++ linux-2.4.20-pre3-bkn1/Documentation/filesystems/devfs/README Sun Aug 18 16:16:01 2002
@@ -727,7 +727,11 @@
mount(8) programme uses /proc/partitions as part of
the volume label search process, and the device names it finds are not
available, because setting CONFIG_DEVFS_FS=y changes the names in
-/proc/partitions, irrespective of whether devfs is mounted.
+/proc/partitions, irrespective of whether devfs is mounted. Another
+exception is if the device nodes in the underlying /dev have been
+deleted. Even if devfs is enabled, it cannot be used if it is not
+mounted (the on-disk /dev will be used instead, unless/until devfs
+is mounted).
Now you've finished all the steps required. You're now ready to boot
your shiny new kernel. Enjoy.