Linux Container Development
 help / color / mirror / Atom feed
From: Eelco Chaudron <echaudron-SvgryPHmmKB+XZJcv9eMoEEOCMrvLtNR@public.gmane.org>
To: "Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
	<Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Network namespace status
Date: Fri, 22 Aug 2008 09:55:09 +0200	[thread overview]
Message-ID: <C4D43D7D.E5BC%echaudron@extremenetworks.com> (raw)

Hi All,

I'm looking at the network namespace status page, http://lxc.sourceforge.net/network/status.php, and according to the header it's updated a while back (march 27th).

I was wondering if some one could share some more details on what still needs to be done, and what the overall status is. Is it ready for prime time?

Thanks,

Eelco
________________________________
DISCLAIMER:
This e-mail and any attachments to it may contain confidential and proprietary material and is solely for the use of the intended recipient. Any review, use, disclosure, distribution or copying of this transmittal is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed.

             reply	other threads:[~2008-08-22  7:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-22  7:55 Eelco Chaudron [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-15 15:31 Network namespace status Daniel Lezcano
2007-09-13 19:12 Network Namespace status Eric W. Biederman
2007-09-14  6:03 ` Oliver Hartkopp
2007-09-14  9:33   ` Eric W. Biederman
2007-09-16 22:36 ` David Miller
2007-09-16 23:47   ` Eric W. Biederman

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=C4D43D7D.E5BC%echaudron@extremenetworks.com \
    --to=echaudron-svgryphmmkb+xzjcv9emoeeocmrvltnr@public.gmane.org \
    --cc=Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox