2.4.20 (ramdisk device naming at boot time(/dev/ramdisk/<n>) vs. after devfs is mounted(/dev/rd/<n>))

• Next message: Ross Biro: "[RFC]: Changes to ide_task_request"
• Previous message: Gabriel Paubert: "[PATCH] Cleanup of the lcall7/lcall27 entry path."
• Next in thread: Brian Jackson: "Re: 2.4.20 (ramdisk device naming at boot time(/dev/ramdisk/<n>) vs. after devfs is mounted(/dev/rd/<n>))"
• Reply: Brian Jackson: "Re: 2.4.20 (ramdisk device naming at boot time(/dev/ramdisk/<n>) vs. after devfs is mounted(/dev/rd/<n>))"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

In the 2.4.20 kernel, when using DEVFS the ramdisk naming is
inconsistent. /dev/ramdisk/0 works for the kernel parameter initrd=
while /dev/rd/0 works in fstab.
For clarity: before DEVFS loads it must be referenced as /dev/ramdisk/0,
yet DEVFS registers /dev/rd/<n>

/)dam.. . . D o n ' t S t o p

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

• Next message: Ross Biro: "[RFC]: Changes to ide_task_request"
• Previous message: Gabriel Paubert: "[PATCH] Cleanup of the lcall7/lcall27 entry path."
• Next in thread: Brian Jackson: "Re: 2.4.20 (ramdisk device naming at boot time(/dev/ramdisk/<n>) vs. after devfs is mounted(/dev/rd/<n>))"
• Reply: Brian Jackson: "Re: 2.4.20 (ramdisk device naming at boot time(/dev/ramdisk/<n>) vs. after devfs is mounted(/dev/rd/<n>))"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed Jan 15 2003 - 22:00:55 EST