On Fri, Dec 19, 2003 at 08:57:25PM +0100, Andreas Janssen wrote: > >> The reason for this can be that you have devfs enabled in your > >> kernel, but are not using it.
> > That makes sense. I noticed a rant about the need for devfs in > > CD-Writing-HOWTO-2.html at linux.org. Perhaps I should be using it, > > then. Is it generally a good idea and what do I have to do to > > convert? > > I don't use it. You need additional software (the devfsd), you need to > take care that symlinks are created to make the new system compatible > with programs that want to use the old device entries (this seems to be > reasonably preconfigured) and so on. Personally I don't know what I recently installed devfsd on my system (I believe that a 2.4 kernel is needed to support devfs). After installing I checked my kernel-image for support: jrpenn 2[0]# grep DEVFS /boot/config-2.4.22-1-k7 CONFIG_DEVFS_FS=y # CONFIG_DEVFS_MOUNT is not set # CONFIG_DEVFS_DEBUG is not set All I needed to change was /etc/default/devfsd: # mount on boot? MOUNT=yes # default no After a reboot the symlinks for backward compatability were already configured in devfsd by the package maintainer. Read /usr/share/doc/devfsd/README.Debian for details. For the devfs faq: http://www.atnf.csiro.au/people/rgooch/linux/docs/devfs.html Note that devfs is now obsolete. It will be replaced by udev. Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
