netdev
[Top] [All Lists]

Re: [PATCH 2.6 NET] Device name changing via rtnetlink

To: Thomas Graf <tgraf@xxxxxxx>
Subject: Re: [PATCH 2.6 NET] Device name changing via rtnetlink
From: Jean Tourrilhes <jt@xxxxxxxxxxxxxxxxxx>
Date: Fri, 10 Sep 2004 13:13:02 -0700
Address: HP Labs, 1U-17, 1501 Page Mill road, Palo Alto, CA 94304, USA.
Cc: netdev@xxxxxxxxxxx
E-mail: jt@hpl.hp.com
In-reply-to: <20040910200644.GJ20088@postel.suug.ch>
Organisation: HP Labs Palo Alto
References: <20040910195003.GA13912@bougret.hpl.hp.com> <20040910200644.GJ20088@postel.suug.ch>
Reply-to: jt@xxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.28i
On Fri, Sep 10, 2004 at 10:06:44PM +0200, Thomas Graf wrote:
> * Jean Tourrilhes <20040910195003.GA13912@xxxxxxxxxxxxxxxxxx> 2004-09-10 12:50
> > Thomas Graf wrote :
> > > 
> > > Allows changing of device name via rtnetlink. Last bit needed to do full
> > > link configuration via rtnetlink.
> > > 
> > > Signed-off-by: Thomas Graf <tgraf@xxxxxxx>
> > 
> >     This does not work, because you don't return the new name to
> > user space. If the new name is a pattern, such as "eth%d" or "wlan%d",
> > you absolutely need to return the new instanciated device name to user
> > space so that userspace doesn't loose track of the device.
> 
> The ifindex stays the same, therefore the user space application can
> simply dump the link list and fetch the new interface name.

        It's so simple to return the new name, so why not do it ?
There is no need to make applications more complex.

> It would
> theoretically be possible to provide the new name via an ACK but
> this would break the RFC.

        What do you mean, break the RFC ?

        Jean

<Prev in Thread] Current Thread [Next in Thread>