On Fri, 14 Jun 2002 18:05:01 -0500 "Derrick 'dman' Hudson" <[EMAIL PROTECTED]> wrote:
> The only odd thing I've noticed is the root= parameter to the kernel. > That must be the old name. I have no idea why, but trying the devfs > name fails. > > Here's my grub stanza for booting the pre-packaged kernel : > > > title Debian GNU/Linux (2.4.18-k7 , 1280x1024x16) > root (hd0,0) > kernel /boot/vmlinuz-2.4.18-k7 root=/dev/hda1 read-only devfs=mount > video=vesa vga=0x31A > initrd /boot/initrd.img-2.4.18-k7 I think I now understand the problem. Grub really doesn't understand devfsd. It just "mounts" the kernel (root=) and lets it take over from there. Thanks for the clarification. Now, would enabling devfsd magically cause my disk-based /dev/ directory to be mirrored in devfs-pace? I'm particularly concerned about the permission and ownership of the devices. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
