On Sun, Jul 27, 2003 at 01:49:19AM +0530, Balram Adlakha wrote:
> On Sat, Jul 26, 2003 at 08:37:50PM +0200, Wiktor Wodecki wrote:
> > On Sat, Jul 26, 2003 at 11:22:14PM +0530, Balram Adlakha wrote:
> > > The old naming scheme is (quite) depricated. Firstly, devfs shows only those devices which are probed (have a driver), secondly the devices are sorted in an easy to understand directory heirarchy to reduce clutter.
> > > Theres a devfs daemon called devfsd which is actually (almost) a part of a working devfs system. Using devfsd, you can autoload modules even while using devfs, and it also creates symlinks to older device name if that is specified in the /etc/devfsd.conf file.
> > > It is your choice if you want to use devfs or not, linux is all about choice. If you don't like the new naming scheme, you can edit a few lines in the devfs source and change the scheme. Or you can have devfs mounted in another place (like /dev2) and create a script which creates symlinks from /dev2 to /dev with your own preferred names, and you can edit /etc/rc.d/rc.sysinit to run the script on bootup.
> > > Or you can continue using the old device inodes...Some people still prefer them.
> > 
> > I understand that and I greatly appreciate the new naming scheme.
> > However it would have been nice if I could have bootet just up and look
> > at it without changing my core system files (I regard /etc/fstab as
> > core). Nevermind, I might give it another shot on a testing system.
> > 
> You won't need to update /etc/fstab if you use devfsd and its configured to create old device names in /dev...

ah! This should be placed somewhere in a FAQ or so. As I've read through
the docs this isn't mentioned anywhere. This of course solves all my
concerns about devfs. Will try it again soon.
Thanks for enlightment :-)

-- 
Regards,

Wiktor Wodecki