From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail138.messagelabs.com (mail138.messagelabs.com [216.82.249.35]) by kanga.kvack.org (Postfix) with ESMTP id 0A1CE6B004D for ; Fri, 27 Feb 2009 09:34:06 -0500 (EST) Received: from d06nrmr1806.portsmouth.uk.ibm.com (d06nrmr1806.portsmouth.uk.ibm.com [9.149.39.193]) by mtagate1.uk.ibm.com (8.13.1/8.13.1) with ESMTP id n1REY3JL006040 for ; Fri, 27 Feb 2009 14:34:03 GMT Received: from d06av01.portsmouth.uk.ibm.com (d06av01.portsmouth.uk.ibm.com [9.149.37.212]) by d06nrmr1806.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id n1REY3jY2560080 for ; Fri, 27 Feb 2009 14:34:03 GMT Received: from d06av01.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av01.portsmouth.uk.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n1REY2Vq007837 for ; Fri, 27 Feb 2009 14:34:03 GMT Message-ID: <49A7F9D7.4060907@free.fr> Date: Fri, 27 Feb 2009 15:33:59 +0100 From: Cedric Le Goater MIME-Version: 1.0 Subject: Re: How much of a mess does OpenVZ make? ;) Was: What can OpenVZ do? References: <1234467035.3243.538.camel@calx> <20090212114207.e1c2de82.akpm@linux-foundation.org> <1234475483.30155.194.camel@nimitz> <20090212141014.2cd3d54d.akpm@linux-foundation.org> <1234479845.30155.220.camel@nimitz> <20090226162755.GB1456@x200.localdomain> <20090226173302.GB29439@elte.hu> <1235673016.5877.62.camel@bahia> <20090226221709.GA2924@x200.localdomain> <1235726349.4570.7.camel@bahia> <20090227105306.GB2939@x200.localdomain> In-Reply-To: <20090227105306.GB2939@x200.localdomain> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: Alexey Dobriyan Cc: Greg Kurz , linux-api@vger.kernel.org, containers@lists.linux-foundation.org, mpm@selenic.com, linux-kernel@vger.kernel.org, Dave Hansen , linux-mm@kvack.org, tglx@linutronix.de, viro@zeniv.linux.org.uk, hpa@zytor.com, Ingo Molnar , torvalds@linux-foundation.org, Andrew Morton , xemul@openvz.org List-ID: > How do you restore set of uts_namespace's? clone(CLONE_NEWUTS); sethostname(...) > Kernel never exposes to userspace which are the same, which are independent. I think you are addressing the problem from a kernel POV. If you see it from the user POV, what he cares about is what the gethostname() returns and not 'struct uts_namespace'. that doesn't mean that C/R shouldn't be aware of the kernel implementation but if you think in terms of user API, it makes life a easier. Cheers, C. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org