[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m17i80l4mt.fsf@frodo.ebiederm.org>
Date: Wed, 22 Oct 2008 14:08:26 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Greg KH <gregkh@...e.de>
Cc: Benjamin Thery <benjamin.thery@...l.net>,
netdev <netdev@...r.kernel.org>,
Dave Miller <davem@...emloft.net>,
Al Viro <viro@....linux.org.uk>,
Serge Hallyn <serue@...ibm.com>,
Daniel Lezcano <dlezcano@...ibm.com>,
linux-kernel@...r.kernel.org, Tejun Heo <htejun@...il.com>,
Denis Lunev <den@...nvz.org>,
Linux Containers <containers@...ts.linux-foundation.org>
Subject: Re: [PATCH 0/4][RFC] netns: sysfs: add a netns suffix to net device sysfs entries
Greg KH <gregkh@...e.de> writes:
> On Wed, Oct 22, 2008 at 05:21:44PM +0200, Benjamin Thery wrote:
>> Network devices from sub-network namespaces appear in sysfs
>> with a name that looks like this: device_name@...ns_id
>> eg: lo@3, eth0@4e
>
> How does the default udev rules as shipped by most distros handle the
> renaming of the network device if the MAC address is duplicated like it
> will be for these eth devices?
The mac address is not duplicated.
Further devices like eth0@4e are completely unusable to the udev
rules in the initial network namespace because they can not talk
to or affect them.
As I read it Ben's ``solution'' puts entries in sysfs that are
completely unusable to udev.
Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists