Hi there!
I think I have something to add to the discussion about symlinks and
booting problems. If you followed the discussion about the booting, you
know that /dev/cdroms/cdrom0 etc. were not supported during boot. We were
a bit confused about that, since they appear in /dev after boot (even
without devfsd). So indeed, Kevin is right. _Some_ symlinks end up in /dev
anyway, without a user space program like devfsd. It is the compatibility
links that need devfsd.
But why do people (like me) have problems booting from /dev/cdroms/cdrom0
or /dev/discs/disc0/part1? That is because they don't run kernel 2.4.20.
I've compiled it yesterday and it works fine. Apparently, the missing of
those links during boot was considered a bug and is now fixed.
So, the only thing you need devfsd for is to create compatibility symlinks
or to do module autoloading when /dev/floppy/0 is looked up, for instance.
Thanks for all the help,
David
|