Re: Specifying names for tap interfaces

[Iain Hibbert <plunky%rya-online.net@localhost>]

On Sun, 24 Jun 2012, Manuel Bouyer wrote:

> On Sun, Jun 24, 2012 at 07:27:23AM +0100, Iain Hibbert wrote:
> > On Sat, 23 Jun 2012, Manuel Bouyer wrote:
> >
> > > On Sat, Jun 23, 2012 at 10:11:28AM +0100, Iain Hibbert wrote:
> > > > > With the restriction that multiple interfaces can't have the same 
> > > > > label
> > > > > at the same time in a system.
> > > >
> > > > but I don't see why such a restriction should be required. It may be
> > > > useful for something, and if the admin wants to label network interfaces
> > > > the same, that is their perogative.. the driver name is still a unique
> > > > identifier.
> > >
> > > Because the goal is to be able to reference interfaces by label.
> > > If 2 interfaces have the same label, you don't know which one to choose.
> >
> > And thus, you are saying that you can't see a reason to allow it?
>
> No, I'm saying it's incompatible with one of the goal of label, which
> is to have a user-specifed interface identifier.

Sorry, was there a design document for this that I didn't see? This seems
rather like a circular argument and you have not explained the reason for
the restriction.

> If the label is not unique, it can't be used as identifier.

Why not? If you want to select to an item using a label, just have the
tools find the first one with the matching label. Don't worry that there
might be another, it will be hidden if you only use that label, until the
first item has its label removed..

regards,
iain