Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 26 Feb 2003 23:07:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 26 Feb 2003 23:07:26 -0500 Received: from TYO201.gate.nec.co.jp ([210.143.35.51]:62884 "EHLO TYO201.gate.nec.co.jp") by vger.kernel.org with ESMTP id ; Wed, 26 Feb 2003 23:07:25 -0500 To: Kasper Dupont Cc: DervishD , Linux-kernel Subject: Re: About /etc/mtab and /proc/mounts References: <20030219112111.GD130@DervishD> <3E5C8682.F5929A04@daimi.au.dk> Reply-To: Miles Bader System-Type: i686-pc-linux-gnu Blat: Foop From: Miles Bader Date: 27 Feb 2003 13:14:06 +0900 In-Reply-To: <3E5C8682.F5929A04@daimi.au.dk> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1070 Lines: 21 Kasper Dupont writes: > I don't think you can put all the information from /etc/mtab > into /proc/mounts without breaking compatibility. Why? Since the option syntax is regular, presumably programs simply ignore options they don't understand. No? > My suggestion would be to change it from /etc/mtab to /mtab.d/mtab. Please, no. don't pollute the root (_especially_ with little one-use directories like that). /var is clearly the right place for this; if /var isn't mounted initially, I'd suggest that mount should simply not update any file at that point, and the init-script that mounts /var can be responsible from propagating information from /proc/mounts to /var/whatever. -Miles -- "I distrust a research person who is always obviously busy on a task." --Robert Frosch, VP, GM Research - 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/