Re: Specifying names for tap interfaces

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Sat, Jun 23, 2012 at 10:43:20AM +0200, Gert Doering wrote:
> Hi,
> 
> On Fri, Jun 22, 2012 at 05:42:36PM +0200, Manuel Bouyer wrote:
> > a way to associate an interface name with its driver name is a must have. 
> 
> I'm not sure I fully understand this argument.  Why does the driver name
> have to be visible in the name of the interface?  I know that "all BSDs

I didn't say it has to be encoded in the name. I said there has to
be an easy way to associate an interface name with its driver.
This could be in ifconfig output, for example.

> have ever done it that way" - but then, you have it in the kernel boot
> messages, for those who really need to know "ah, eth3 is wm, eth4 is em"...
> 
> As a sysadmin, I find it actually somewhat annoying that my interface
> name changes if I happen to swap a broken network card vs. another one

This is where label would help :)

> with a different chip on it, instead of "the first ethernet interface" 
> reliably being "eth0".

The problem is that "the first" interface can change too.

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--