Linux Container Development
 help / color / mirror / Atom feed
From: Cedric Le Goater <legoater-GANU6spQydw@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers
	<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
	lxc-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Kernel 2.6.33-rc6, 3 bugs container specific.
Date: Thu, 04 Feb 2010 17:02:21 +0100	[thread overview]
Message-ID: <4B6AEF8D.1050005@free.fr> (raw)
In-Reply-To: <20100204151927.GA7556-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>

On 02/04/2010 04:19 PM, Serge E. Hallyn wrote:
> I still like your syslog command 11, but assuming we want to keep the
> syslog_ns on nsproxy, I think we really need to stick to clone/unshare.

Yes. let's keep the namespace creation API consistent. this is complex
enough.

C.

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com

  parent reply	other threads:[~2010-02-04 16:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1265074676.6260.212.camel@Mercier.safe.ca>
     [not found] ` <20100202031647.GA14318@fqdn.org>
     [not found]   ` <1265121846.6260.231.camel@Mercier.safe.ca>
     [not found]     ` <4B68649D.2000503@free.fr>
     [not found]       ` <4B68649D.2000503-GANU6spQydw@public.gmane.org>
2010-02-02 18:18         ` Kernel 2.6.33-rc6, 3 bugs container specific Serge E. Hallyn
     [not found]           ` <20100202181801.GA28412-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-02 18:43             ` Jean-Marc Pigeon
     [not found]               ` <1265136215.6260.261.camel-4BUXZ/Ty1v7iqR6jatDSCA@public.gmane.org>
2010-02-02 21:32                 ` Serge E. Hallyn
     [not found]                   ` <20100202213254.GH32305-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-03 10:51                     ` Daniel Lezcano
     [not found]                       ` <4B695535.7020301-GANU6spQydw@public.gmane.org>
2010-02-03 13:24                         ` Jean-Marc Pigeon
2010-02-03 15:03                         ` Serge E. Hallyn
     [not found]                           ` <20100203150350.GA7146-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-03 15:48                             ` Jean-Marc Pigeon
     [not found]                               ` <1265212090.6260.284.camel-4BUXZ/Ty1v7iqR6jatDSCA@public.gmane.org>
2010-02-03 16:21                                 ` Serge E. Hallyn
2010-02-04  9:33                             ` Daniel Lezcano
     [not found]                               ` <4B6A9461.1010309-GANU6spQydw@public.gmane.org>
2010-02-04 15:19                                 ` [Lxc-users] " Serge E. Hallyn
     [not found]                                   ` <20100204151927.GA7556-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-04 16:02                                     ` Cedric Le Goater [this message]
2010-02-02 14:46 Jean-Marc Pigeon

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=4B6AEF8D.1050005@free.fr \
    --to=legoater-ganu6spqydw@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=lxc-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=serue-r/Jw6+rmf7HQT0dZR+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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox