2003-01-15 17:44:34

by Adam Scislowicz

[permalink] [raw]
Subject: 2.4.20 (ramdisk device naming at boot time(/dev/ramdisk/<n>) vs. after devfs is mounted(/dev/rd/<n>))

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


2003-01-15 18:17:10

by Brian Jackson

[permalink] [raw]
Subject: Re: 2.4.20 (ramdisk device naming at boot time(/dev/ramdisk/<n>) vs. after devfs is mounted(/dev/rd/<n>))

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

--Brian Jackson

On Wednesday 15 January 2003 11:56 am, Adam Scislowicz wrote:
> 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/