From: "Serge E. Hallyn" <serge@hallyn•com>
To: Mark Ryden <markryde@gmail•com>
Cc: Greg KH <gregkh@suse•de>, David Shwatrz <dshwatrz@gmail•com>,
Tejun Heo <htejun@gmail•com>, Greg KH <greg@kroah•com>,
linux-kernel@vger•kernel.org, netdev@vger•kernel.org,
"Eric W. Biederman" <ebiederm@xmission•com>,
Al Viro <viro@ftp•linux.org.uk>,
Linux Containers <containers@lists•osdl.org>,
Andrew Morton <akpm@linux-foundation•org>,
Daniel Lezcano <dlezcano@fr•ibm.com>,
Benjamin Thery <benjamin.thery@bull•net>
Subject: Re: sysfs tagged directory support status (was:. Re: [PATCH 1/8] sysfs: Implement sysfs tagged directory support)
Date: Sun, 5 Apr 2009 23:49:58 -0500 [thread overview]
Message-ID: <20090406044958.GA8644@hallyn.com> (raw)
In-Reply-To: <dac45060904052128p6c539fe4p199a03f47a43a96b@mail.gmail.com>
Quoting Mark Ryden (markryde@gmail•com):
> Hello,
> I am sorry to hear that it is not merged yet.I hoped to try to start a
> project with network namespaces.
Sysfs tagged directories are not supported, but with 2.6.29 you
can use network namespaces. There are some limits - you can't
move a physical network device out of the initial network
namespace, and (veth) devices which are not in the initial
network namespace just don't show up in /sys/class/net (since
we can't tag them).
But you can use network namespaces.
-serge
prev parent reply other threads:[~2009-04-06 4:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 10:00 sysfs tagged directory support status (was:. Re: [PATCH 1/8] sysfs: Implement sysfs tagged directory support) Mark Ryden
2009-04-04 3:05 ` Greg KH
2009-04-06 4:28 ` Mark Ryden
2009-04-06 4:49 ` Serge E. Hallyn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090406044958.GA8644@hallyn.com \
--to=serge@hallyn$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=benjamin.thery@bull$(echo .)net \
--cc=containers@lists$(echo .)osdl.org \
--cc=dlezcano@fr$(echo .)ibm.com \
--cc=dshwatrz@gmail$(echo .)com \
--cc=ebiederm@xmission$(echo .)com \
--cc=greg@kroah$(echo .)com \
--cc=gregkh@suse$(echo .)de \
--cc=htejun@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=markryde@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=viro@ftp$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox