lkml.org 
[lkml]   [2008]   [Oct]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 0/4][RFC] netns: sysfs: add a netns suffix to net device sysfs entries
On Wed, 22 Oct 2008 14:01:59 -0700
ebiederm@xmission.com (Eric W. Biederman) wrote:

> "Serge E. Hallyn" <serue@us.ibm.com> writes:
>
> > Quoting Eric W. Biederman (ebiederm@xmission.com):
> >> Benjamin Thery <benjamin.thery@bull.net> writes:
> >>
> >> > Support for network namespaces in mainline is pretty complete for
> >> > some time now, but there is still this issue with sysfs that prevents
> >> > more people to use it easily.
> >>
> >> Ben your patchset is completely inappropriate.
> >>
> >> Temporarily adding elements to the ABI that we intend to remove
> >> is not a proper solution to this problem.
> >>
> >> That user space visible ida you add is a namespace identifier that breaks
> >> nested containers and migration. It is very very very wrong.
> >
> > I disagree (not surprising :) completely. The well-known userspace
> > tools (ifconfig, ip, etc) will not see the lo@1, they'll see lo.
> > Userspace in a container can either umount /sys completely, or do
>
> The well-known user space tools don't use /sys at all. Modern
> network tools use rtnetlink (ip) old network tools use /proc/net.
>
> Very few things actually use /sys and for those things lo@1 or
> eth0@1 are completely useless except for implementing a FUSE
> mock up of sysfs. But you don't need anything in sysfs to do
> that as all of the interesting information is available through
> /proc/net or rtnetlink.

Lots of scripts are starting use /sys for things. It is easier to
parse /sys/class/net than the output of ifconfig or ip


\
 
 \ /
  Last update: 2008-10-22 23:57    [W:0.060 / U:7.360 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site