From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757061AbZB0Of2 (ORCPT ); Fri, 27 Feb 2009 09:35:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752652AbZB0OfQ (ORCPT ); Fri, 27 Feb 2009 09:35:16 -0500 Received: from mtagate5.uk.ibm.com ([195.212.29.138]:42974 "EHLO mtagate5.uk.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752069AbZB0OfO (ORCPT ); Fri, 27 Feb 2009 09:35:14 -0500 Message-ID: <49A7F9D7.4060907@free.fr> Date: Fri, 27 Feb 2009 15:33:59 +0100 From: Cedric Le Goater User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 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 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: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > 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.