Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 20 Nov 2001 14:45:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 20 Nov 2001 14:45:14 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:42252 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Tue, 20 Nov 2001 14:43:33 -0500 Message-ID: <3BFAB25B.2080200@zytor.com> Date: Tue, 20 Nov 2001 11:43:23 -0800 From: "H. Peter Anvin" Organization: Zytor Communications User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010913 X-Accept-Language: en, sv MIME-Version: 1.0 To: Andries.Brouwer@cwi.nl CC: linux-kernel@vger.kernel.org Subject: Re: Linux can use a mountpoint for 2 Filesystems In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Andries.Brouwer@cwi.nl wrote: > hpa: > > >>There are real reasons to overmount a filesystem. It's getting to be >>a usability problem, probably because Linux (UNLIKE MOST OTHER UNIXES) >>didn't allow it until just recently. This change caused some >>problems, including with the automount daemon. I would like to see an >>option to mount(8) to allow it, by default disallow by policy. >> > > mount(8) does not necessarily have such information: > /etc/mtab is just a random file with random contents, > and /proc/mounts need not exist. > > The cleanest way to do what you suggest would be to make the kernel > refuse an overmount unless the mount(2) flags included the > "overmount" flag. > Agreed. -hpa - 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/