[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081022212417.GA10265@suse.de>
Date: Wed, 22 Oct 2008 14:24:17 -0700
From: Greg KH <gregkh@...e.de>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
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
On Wed, Oct 22, 2008 at 02:08:26PM -0700, Eric W. Biederman wrote:
> 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.
Ah, ok, I really don't think I want to know more :)
> 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.
Oh, good point.
> As I read it Ben's ``solution'' puts entries in sysfs that are
> completely unusable to udev.
That's not a good thing to do, if udev can't see them, than HAL can't
see them, then the rest of userspace usually has no idea they are
present either.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists