Skip to contentSkip to conversation

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

DISCUSSION Adam Scislowicz 2 participants 2 messages Jan 15, 2003

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw

devfsd.conf has some stuff in it about making symlinks. Maybe this would work for you. It is worth a look.

--Brian Jackson

Quoted 13 lines · Adam Scislowicz

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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/