Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755209AbYA3BzN (ORCPT ); Tue, 29 Jan 2008 20:55:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754684AbYA3Bys (ORCPT ); Tue, 29 Jan 2008 20:54:48 -0500 Received: from scrub.xs4all.nl ([194.109.195.176]:2494 "EHLO scrub.xs4all.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753625AbYA3Byl (ORCPT ); Tue, 29 Jan 2008 20:54:41 -0500 From: Roman Zippel To: Miklos Szeredi Subject: Re: [patch 01/26] mount options: add documentation Date: Wed, 30 Jan 2008 02:54:04 +0100 User-Agent: KMail/1.9.7 Cc: akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Steve French , Lachlan McIlroy , "Josef 'Jeff' Sipek" , Russell King , David Howells , Ian Kent , "Sergey S. Kostyliov" , Karsten Keil , "H. Peter Anvin" , "Theodore Ts'o" , OGAWA Hirofumi , Jeff Dike , Mikulas Patocka , William Irwin , Dave Kleikamp , Petr Vandrovec , Trond Myklebust , Jeff Mahoney , Paul Mackerras , Hugh Dickins , Cyrill Gorcunov , Greg Kroah-Hartman References: <20080124193341.166753833@szeredi.hu> <20080124193416.379218079@szeredi.hu> In-Reply-To: <20080124193416.379218079@szeredi.hu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801300254.06363.zippel@linux-m68k.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1124 Lines: 28 Hi, On Thursday 24. January 2008, Miklos Szeredi wrote: > Q: Why do we need correct option showing in /proc/mounts? > A: We want /proc/mounts to fully replace /etc/mtab. The reasons for > this are: > - unprivileged mounters won't be able to update /etc/mtab > - /etc/mtab doesn't work with private mount namespaces > - /etc/mtab can become out-of-sync with reality I asked this before and I don't remember getting an answer: How does this deal with certain special cases: - chroot: how will mount/df only show the for chroot relevant mounts? - loop: how is the connection between file and loop device maintained? I don't quite see how you want to achieve a _full_ replacement. Could also please explain why you want to go via user mounts. Other OS use a daemon for that, which e.g. can maintain access controls. How do you want to manage this? bye, Roman -- 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/