From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH] private mounts Date: Sat, 30 Apr 2005 09:37:42 +0100 Message-ID: <20050430083742.GD23253@infradead.org> References: <20050424201820.GA28428@infradead.org> <20050424205422.GK13052@parcelfarce.linux.theplanet.co.uk> <20050424210616.GM13052@parcelfarce.linux.theplanet.co.uk> <20050424211942.GN13052@parcelfarce.linux.theplanet.co.uk> <20050425094804.GA33040@dspnet.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:20142 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S261159AbVD3Ihr (ORCPT ); Sat, 30 Apr 2005 04:37:47 -0400 To: Olivier Galibert , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Content-Disposition: inline In-Reply-To: <20050425094804.GA33040@dspnet.fr.eu.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, Apr 25, 2005 at 11:48:04AM +0200, Olivier Galibert wrote: > On Sun, Apr 24, 2005 at 10:19:42PM +0100, Al Viro wrote: > > Of course you can. It does execute the obvious set of rc files. > > Is there a possibility for a process to change its namespace to > another existing one? That would be needed to have a per-user > namespace you go to from rc files or pam. It is not right now, and I don't think joining a namespace is a concept that fits very well into our architecture. What does make sense is an unshare() syscall that takes the CLONE_* argument and unshares those in the current process from the parent without creating a new process. Then you can easily reproduce another namespace by value instead of by reference.