Date: Sun, 09 Apr 2006 03:27:42 +0200 From: Daniel Rock <freebsd@deadcafe.de> To: hackers@freebsd.org Subject: Re: Using any network interface whatsoever Message-ID: <4438630E.4090300@deadcafe.de> In-Reply-To: <44384A55.2010103@samsco.org> References: <C05CAC06.C0BD%ceri@submonkey.net> <20060407225742.GA21619@odin.ac.hmc.edu> <20060407230247.GH16344@submonkey.net> <4437C9F6.5000008@samsco.org> <20060408233740.GA84768@submonkey.net> <44384A55.2010103@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Scott Long schrieb: > Ceri Davies wrote: > >> On Sat, Apr 08, 2006 at 08:34:30AM -0600, Scott Long wrote: > >>> Well, the real question is why we force the details of driver names >>> onto users. Network and storage drivers are especially guilty of >>> this, but tty devices also are annoying. How do you know which manual page to read for driver specifics if they are all named eth0, eth1, ... With the current naming scheme you know when to read the man page for em(4), fxp(4), nve(4), ... > I'll say again, how does having em0, em1, em2, and em3 help me know what > is going on with each of those interfaces? FreeBSD doesn't support persistent instance numbering, unlike Solaris. If you unplug device em0 in FreeBSD the remaining interfaces get renamed em0, em1, em2 - which is a bad thing. If you unplug e1000g0 in Solaris the remaining interfaces will still be named e1000g1, e1000g2, e1000g3. So I doubt that the overwriting of an Ingres database really happened in Solaris, like some other poster described - unless the administrator fiddled with /etc/path_to_inst by hand (you are free to shoot in your own foot). Daniel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4438630E.4090300>