Date: Sat, 08 Apr 2006 17:42:13 -0600 From: Scott Long <scottl@samsco.org> To: Ceri Davies <ceri@submonkey.net> Cc: hackers@freebsd.org Subject: Re: Using any network interface whatsoever Message-ID: <44384A55.2010103@samsco.org> In-Reply-To: <20060408233740.GA84768@submonkey.net> References: <C05CAC06.C0BD%ceri@submonkey.net> <20060407225742.GA21619@odin.ac.hmc.edu> <20060407230247.GH16344@submonkey.net> <4437C9F6.5000008@samsco.org> <20060408233740.GA84768@submonkey.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Ceri Davies wrote: > On Sat, Apr 08, 2006 at 08:34:30AM -0600, Scott Long wrote: > >>>>On Fri, Apr 07, 2006 at 11:53:42PM +0100, Ceri Davies wrote: > > >>>>>For the filesystem I can use geom_label and /dev/ufs/UnlikelyString, but >>>>>I'd >>>>>also like to have it try to configure whatever interfaces the machine >>>>>happens to have via DHCP. >>>>> >>>>>Other than specifying ifconfig_<if>0="DHCP" once for every possible >>>>>value of >>>>><if>, is there a mechanism to do this already? >>>> >>>>ifconfig_DEFAULT >> >>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. > > > The current situation on BSD, where I can identify which interface is > meant by its type, is definitely preferable to the Linux situation where > eth0 may mean something different tomorrow depending on what is plugged > in. > > Since we can rename devices arbitrarily, I don't really see a problem > with respect to anything else. > > Ceri I'll say again, how does having em0, em1, em2, and em3 help me know what is going on with each of those interfaces? Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44384A55.2010103>