From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Serge Hallyn <serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
Cc: Harini Donthineni
<harini.donthineni-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: hi regarding the Linux containers
Date: Tue, 30 Apr 2013 15:05:44 -0700 [thread overview]
Message-ID: <87bo8vishz.fsf@xmission.com> (raw)
In-Reply-To: <20130429132509.GB30159@sergelap> (Serge Hallyn's message of "Mon, 29 Apr 2013 08:25:09 -0500")
Serge Hallyn <serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org> writes:
> netns has been supported for quite some time in the kernel, as has
> setns() to netns. You don't need to apply any patches. For
> documentation see the manpages: setns(2), unshare(2), clone(2), and
> finally the still-in-development namespaces(7), for which you can
> see an early draft at https://lkml.org/lkml/2013/3/15/56
A virtual router can mean a lot of things to different folks, but I
would recommend playing with ip(8) aka iproute2. The ip netns family of
commands allow you to configure the most common definitions of a virtual
router.
Eric
prev parent reply other threads:[~2013-04-30 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 17:45 hi regarding the Linux containers Harini Donthineni
[not found] ` <CAHfs=Wzf5cQqoa4Q3EuG3rfp7qQAmDWGfpQQ5Z3H5fzVG3puVA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-29 13:25 ` Serge Hallyn
2013-04-30 22:05 ` Eric W. Biederman [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=87bo8vishz.fsf@xmission.com \
--to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=harini.donthineni-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.