Date: Thu, 28 Jan 1999 19:31:21 +0100 (CET) From: Wilko Bulte <wilko@yedi.iaf.nl> To: sthaug@nethelp.no Cc: archie@whistle.com, dfr@nlsystems.com, current@FreeBSD.ORG Subject: Re: DEVFS, the time has come... Message-ID: <199901281831.TAA00473@yedi.iaf.nl> In-Reply-To: <7987.917514435@verdi.nethelp.no> from "sthaug@nethelp.no" at "Jan 28, 99 10:07:15 am"
next in thread | previous in thread | raw e-mail | index | archive | help
As sthaug@nethelp.no wrote... > > > I agree.. and same thing goes for Ethernet drivers. I actually > > > like the way Linux always has "eth0", "eth1", ... (which we could > > > > Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this > > just a matter of taste or is there more to it? I for one don't see any > > advantage in eth[0-9] style device naming. > > I can give you one example. We run a FreeBSD box here which receives > all of the traffic (port mirroring) from some Ethernet switches. On > the FreeBSD box, we run nnstat, tcpdump etc. for monitoring purposes. > > Recently I changed some of the DEC 21x4x based cards on this box to > Intel cards. Thus the interface names changed from deN to fxpN. This > meant we had to update a bunch of Perl and shell scripts. It would > have been much nicer (no need to update) if the interfaces were simply > named ethN. Hmmm. Well I happen to like the concept of being able to tell straight away what device I'm talking to. eth# style naming does not allow that. But I can understand that other people might feel otherwise. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ 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?199901281831.TAA00473>