Top Post Alert!! After meddling with it and recompiling my kernel w/o DEVFS at all, I managed to get it to work. (though the error has nothing to do with the DEVFS being compiled into the kernel [but not to be mounted automatically])
The error is very...very... very.. subtle and I'm not sure why I have this issue at all. Could be remmants from devfs being mounted automatically at boot?? Anyway.. I found out the file/block device /dev/.devfsd was the reason for it to not be able to go to udev. and since there's a "clear" command in /sbin/rc before it does that "The Gentoo system init....." I didn't catch the error message. The MEssage was .... cannot remove /dev/.devfsf - read only filesystem. So.. the solution was to go to single mode and then remount the root fs read-write and then proceed to delete /dev/.devfsd Yipee.. Now I have udev working. I plug in my USB key, /dev/sda[1] is created and deleted automatically as I plug in/out the key. So.. RIght now, it's working.. Cool. On Mon, 2005-05-09 at 11:46 +0800, Ow Mun Heng wrote: > I tried to upgrade(?) from devfs to udev(045) today and it was > miserable. > > I followed the Gentoo Udev Guide as well as DSD's guide but no go. > > I've recompiled my kernel(2.6.11) to _not_ mount /dev/ automatically at > boot. (devFS is still compiled into the kernel) > > edited /etc/conf.d/rc > RC_DEVICES="auto" > RC_DEVICE_TARBALL="yes" > RC_DEVFSD_STARTUP="yes" > > changed my kernel (grub) line to append gentoo=nodevfs > > Rebooted and faced a lot of issues. > > The 1st would be the obvious /sbin/rc file : > > The Gentoo Linux system initialization scripts have detected that" > your system does not support DEVFS or UDEV. Since Gentoo Linux" > has been designed with these dynamic /dev managers in mind, it is" > highly suggested that you build support for it into your kernel." > Please read the Gentoo Handbook for more information!" > > I continue booting and I find that in the _worst_ case, I can't load > up /dev/hda3 (root) due to a missing/invalid/non-existant symlink > in /dev > > I tried executing udevstart and it spurt out these (bunch of) lines > in /var/log/messages > > configured rule in '/etc/udev/rules.d/50-udev.rules' at line 133 > applied, added symlink '%k' > > configured rule in '/etc/udev/rules.d/50-udev.rules' at line 133 > applied, 'vcs3' becomes 'vcc/%n' > > > I tried a few variants but all of them no go. I finally relented and > removed udev and reverted back to my old kernel (/dev/ mounted > automatically at boot) > > I boot into the original kernel and now I see these errors : > > devfs_mk_dev: could not append to parent for vcc/2 > devfs_mk_dev: could not append to parent for vcc/3 > devfs_mk_dev: could not append to parent for vcc/a3 > devfs_mk_dev: could not append to parent for vcc/4 > devfs_mk_dev: could not append to parent for vcc/a4 > > Guys... There are 2 ways to fix this. > > 1. Help me get udev running again. (but why do I need udev anyway??) > 2. Help me get devfs running again. Right now.. I see it's only those > few errors above and everything seems to be working. > > > > > -- > Ow Mun Heng > Gentoo/Linux on DELL D600 1.4Ghz > 98% Microsoft(tm) Free!! > Neuromancer 11:31:20 up 25 min, 5 users, load average: 1.48, 1.39, 0.87 > > -- Ow Mun Heng Gentoo/Linux on DELL D600 1.4Ghz 98% Microsoft(tm) Free!! Neuromancer 14:37:00 up 18 min, 5 users, load average: 0.31, 0.63, 0.59 -- [email protected] mailing list
