Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030435AbWBHSbR (ORCPT ); Wed, 8 Feb 2006 13:31:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030436AbWBHSbQ (ORCPT ); Wed, 8 Feb 2006 13:31:16 -0500 Received: from e3.ny.us.ibm.com ([32.97.182.143]:21945 "EHLO e3.ny.us.ibm.com") by vger.kernel.org with ESMTP id S1030435AbWBHSbQ (ORCPT ); Wed, 8 Feb 2006 13:31:16 -0500 Message-ID: <43EA38F0.20107@watson.ibm.com> Date: Wed, 08 Feb 2006 13:31:12 -0500 From: Hubertus Franke User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Serge E. Hallyn" CC: "Eric W. Biederman" , Sam Vilain , Rik van Riel , Kirill Korotaev , Linus Torvalds , Andrew Morton , linux-kernel@vger.kernel.org, clg@fr.ibm.com, haveblue@us.ibm.com, greg@kroah.com, alan@lxorguk.ukuu.org.uk, arjan@infradead.org, kuznet@ms2.inr.ac.ru, saw@sawoct.com, devel@openvz.org, Dmitry Mishin , Andi Kleen , Herbert Poetzl Subject: Re: The issues for agreeing on a virtualization/namespaces implementation. References: <43E83E8A.1040704@vilain.net> <43E8D160.4040803@watson.ibm.com> <20060207201908.GJ6931@sergelap.austin.ibm.com> <43E90716.4020208@watson.ibm.com> <43E92EDC.8040603@watson.ibm.com> <43EA02D6.30208@watson.ibm.com> <20060208180309.GA20418@sergelap.austin.ibm.com> In-Reply-To: <20060208180309.GA20418@sergelap.austin.ibm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1273 Lines: 37 Serge E. Hallyn wrote: > Quoting Hubertus Franke (frankeh@watson.ibm.com): > >>IMHO, there is only a need to refer to a namespace from the global context. >>Since one will be moving into a new container, but getting out of one >>could be prohibitive (e.g. after migration) >>It does not make sense therefore to know the name of a namespace in >>a different container. > > > Not sure I agree. What if we are using a private namespace for a > vserver, and then we want to create a private namespace in there for a > mobile application. Since we're talking about nested namespaces, this > should be possible. > > Now I believe Eric's code so far would make it so that you can only > refer to a namespace from it's *creating* context. Still restrictive, > but seems acceptable. > That's what I meant .. as usually used the wrong word.. s/global context/spawing context/g .. because that's the only place where you have a pid to refer to the newly created container ! > (right?) > Yes, seriii .. ahmm serue > -serge > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/