From: Michael Kerrisk <mtk.manpages@googlemail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Pavel Emelyanov <xemul@openvz.org>,
David Miller <davem@davemloft.net>,
"Eric W. Biederman" <ebiederm@xmission.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-man@vger.kernel.org,
Subrata Modak <subrata@linux.vnet.ibm.com>,
Stephen Hemminger <shemminger@linux-foundation.org>,
adobriyan@gmail.com, Patrick McHardy <kaber@trash.net>,
den@openvz.org, Daniel Lezcano <dlezcano@fr.ibm.com>
Subject: Current state of Network Namespaces (NETNS, CLONE_NEWNET)?
Date: Wed, 19 Nov 2008 16:49:05 -0500 [thread overview]
Message-ID: <492489D1.5080502@gmail.com> (raw)
Sorry for the shotgun mail, but in the end, it's
not clear who can best answer my question(s).
I'm currently trying to add documentation of all of
the undocumented CLONE_* flags. One of these is
CLONE_NEWNET, and I could use (quite a lot of) help.
My questions:
What is the current state of the network namespace
implementation? Is it complete?
What objects are considered part of the network
namespace, and therefore distinct for a new network
namespace?
Is there any documentation for network namespaces
already?
Are there any test programs for network namespaces?
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
next reply other threads:[~2008-11-19 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 21:49 Michael Kerrisk [this message]
2008-11-20 1:37 ` Current state of Network Namespaces (NETNS, CLONE_NEWNET)? Eric W. Biederman
2008-11-20 2:50 ` Alexey Dobriyan
2008-11-20 7:54 ` Daniel Lezcano
2008-11-20 8:04 ` Subrata Modak
2008-11-20 18:20 ` CLONE_NEWNET documentation Michael Kerrisk
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=492489D1.5080502@gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=adobriyan@gmail.com \
--cc=davem@davemloft.net \
--cc=den@openvz.org \
--cc=dlezcano@fr.ibm.com \
--cc=ebiederm@xmission.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=subrata@linux.vnet.ibm.com \
--cc=xemul@openvz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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