Date: Mon, 10 Apr 2006 18:24:12 -0700 From: Joseph Scott <joseph@randomnetworks.com> To: Darren Pilgrim <darren.pilgrim@bitfreak.org> Cc: mwm-keyword-freebsdhackers.102a7e@mired.org, scottl@samsco.org, ceri@submonkey.net, hackers@FreeBSD.org Subject: Re: Using any network interface whatsoever Message-ID: <40B160C1-719B-4FCA-A192-75432F3738D5@randomnetworks.com> In-Reply-To: <443ACCB6.8080306@bitfreak.org> References: <20060409090757.GW80492@spc.org> <20060409.184825.99254285.imp@bsdimp.com> <20060410194746.GY80492@spc.org> <20060410.141042.25162164.imp@bsdimp.com> <443ACCB6.8080306@bitfreak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 10, 2006, at 2:23 PM, Darren Pilgrim wrote: > I think at this point it's been pretty well established that: > > - Device naming and unit numbering is not stable enough to avoid > breakage across hardware changes. > - There is a need for generic and/or descriptive interface naming > independent of driver- and probe-order-based naming. > - There are static bits of information available about each device > in the system that can be used to locate a specific device that > would be sufficient to allow assignment of a network configuration > to a physical device, not it's attached name. > > If I were to write an rc.d script to use descriptive network > interface names and wire configs to static hardware identification, > would there be support for such a feature? Being mostly a lurker on this list I don't know that my vote would count for much, but yes I'd support such a feature. Thank you also for outlining the issues for this thread in a simple manner. -- Joseph Scott joseph@randomnetworks.com http://joseph.randomnetworks.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40B160C1-719B-4FCA-A192-75432F3738D5>