Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 28 Jan 1999 12:01:57 -0800
From:      Scott Michel <scottm@ulfus.cs.ucla.edu>
To:        Wilko Bulte <wilko@yedi.iaf.nl>
Cc:        freebsd-current@FreeBSD.ORG
Subject:   Re: DEVFS, the time has come... 
Message-ID:  <199901282001.MAA11620@cs.ucla.edu>
In-Reply-To: Your message of "Thu, 28 Jan 1999 19:38:45 %2B0100." <199901281838.TAA00524@yedi.iaf.nl> 

next in thread | previous in thread | raw e-mail | index | archive | help
> Not true IMO. You still need to know what hardware you have before you
> can build your own kernels etc etc. 
> 
> > Also the eth[0..x] thing means you can replace your ethernet card
> > with a new one of a different type without having to look through
> > your config code for references to ed0 or whatever.
> 
> True.

There's no reason why the devfs code couldn't create the equivalent
of symbolic links in its file system so that ed0 and eth0 show up.

Yes, I know, this opens up a can of worms when new hardware is added
and suddenly the probe order changes such that a newbie finds that
eth0 is no longer what he/she/it thought it was going to be. But it's
a start.


-scooter



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901282001.MAA11620>