Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262414AbVDXUuQ (ORCPT ); Sun, 24 Apr 2005 16:50:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262413AbVDXUuQ (ORCPT ); Sun, 24 Apr 2005 16:50:16 -0400 Received: from rev.193.226.232.93.euroweb.hu ([193.226.232.93]:35993 "EHLO dorka.pomaz.szeredi.hu") by vger.kernel.org with ESMTP id S262411AbVDXUuL (ORCPT ); Sun, 24 Apr 2005 16:50:11 -0400 To: hch@infradead.org CC: linux-fsdevel@vger.kernel.org, hch@infradead.org, linux-kernel@vger.kernel.org, akpm@osdl.org In-reply-to: <20050424201820.GA28428@infradead.org> (message from Christoph Hellwig on Sun, 24 Apr 2005 21:18:20 +0100) Subject: Re: [PATCH] private mounts References: <20050424201820.GA28428@infradead.org> Message-Id: From: Miklos Szeredi Date: Sun, 24 Apr 2005 22:50:04 +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 844 Lines: 20 > > This simple patch adds support for private (or invisible) mounts. The > > rationale is to allow mounts to be private for a user but still in the > > global namespace. > > As mentioned in the last -fsdevel thread a few times the idea of per-user > mounts is fundamentally flawed. Crossing a namespace boundary must be > explicit - using clone or a new unshare() syscall. Also mentioned in that thread quite a few times is the fact the the clone() and unshare() modell does not solve people's requirements. Care to read through that thread and suggest an alternative solution? Thanks, Miklos - 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/