From: Daniel Lezcano <dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
To: Babu N <babu.neelam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: Krishna Vamsi-B22174
<avamsi-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
"Eric W. Biederman"
<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Subject: Re: Network Namespace-1000 networks with Overlap Addresses
Date: Thu, 23 Apr 2009 10:39:35 +0200 [thread overview]
Message-ID: <49F02947.3060602@fr.ibm.com> (raw)
In-Reply-To: <200904230820.n3N8KgXW027602-/sMIUUHvcVm7KQohPwX1u+lZC/4ptaCc@public.gmane.org>
Babu N wrote:
> Hi,
>
> I am finding that a unshare call with CLONE_NEWNET is giving error in
> ubuntu 8.10 (kernet version 2.6.27).
> The man page here
> (http://manpages.courier-mta.org/htmlman2/clone.2.html) states that
> CLONE_NEWNET implementation is not yet complete, but probably will be
> mostly complete by about Linux 2.6.28.
> Is there way I can use CLONE_NEWNET successfully in 2.6.27 ?
>
No, in 2.6.27 the netns code is not complete and buggy.
You have to use the 2.6.29 kernel version.
-- Daniel
next prev parent reply other threads:[~2009-04-23 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 2:40 Network Namespace-1000 networks with Overlap Addresses Krishna Vamsi-B22174
[not found] ` <B2EBF6E450E65C4F8CFEE8947E1905600298E2FF-ofAVchDyotZeePcQ0jRo1pjmvxFtTJ+o0e7PPNI6Mm0@public.gmane.org>
2009-04-14 14:37 ` Serge E. Hallyn
[not found] ` <20090414143712.GC6072-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-04-22 10:57 ` Eric W. Biederman
[not found] ` <m11vrlvtva.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
2009-04-23 8:26 ` Babu N
[not found] ` <200904230820.n3N8KgXW027602-/sMIUUHvcVm7KQohPwX1u+lZC/4ptaCc@public.gmane.org>
2009-04-23 8:39 ` Daniel Lezcano [this message]
[not found] ` <49F02947.3060602-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2009-04-23 8:58 ` Daniel Lezcano
[not found] ` <49F02DB6.8020309-GANU6spQydw@public.gmane.org>
2009-04-23 9:48 ` Babu N
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=49F02947.3060602@fr.ibm.com \
--to=dlezcano-nmtc/0zbporqt0dzr+alfa@public.gmane.org \
--cc=avamsi-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=babu.neelam-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@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.