From owner-freebsd-current Thu Jan 28 12:02:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04148 for freebsd-current-outgoing; Thu, 28 Jan 1999 12:02:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cs.ucla.edu (Ulfus.CS.UCLA.EDU [131.179.48.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04122 for ; Thu, 28 Jan 1999 12:02:26 -0800 (PST) (envelope-from scottm@ulfus.cs.ucla.edu) Received: from ulfus.cs.ucla.edu (localhost [127.0.0.1]) by cs.ucla.edu (8.8.7/8.8.8) with ESMTP id MAA11620; Thu, 28 Jan 1999 12:01:57 -0800 Message-Id: <199901282001.MAA11620@cs.ucla.edu> X-Mailer: exmh version 2.0.2 To: Wilko Bulte cc: freebsd-current@FreeBSD.ORG Subject: Re: DEVFS, the time has come... In-Reply-To: Your message of "Thu, 28 Jan 1999 19:38:45 +0100." <199901281838.TAA00524@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Jan 1999 12:01:57 -0800 From: Scott Michel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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