Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 2 Mar 2003 08:19:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 2 Mar 2003 08:19:45 -0500 Received: from [66.70.28.20] ([66.70.28.20]:50449 "EHLO maggie.piensasolutions.com") by vger.kernel.org with ESMTP id ; Sun, 2 Mar 2003 08:18:48 -0500 Date: Sun, 2 Mar 2003 13:53:15 +0100 From: DervishD To: Miles Bader Cc: Kasper Dupont , Linux-kernel Subject: Re: About /etc/mtab and /proc/mounts Message-ID: <20030302125315.GH45@DervishD> References: <20030219112111.GD130@DervishD> <3E5C8682.F5929A04@daimi.au.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4i Organization: Pleyades User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 740 Lines: 19 Hi Miles :) Miles Bader dixit: > /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. In an embedded system I built a time ago, /etc/mtab was first a symlink to /proc/mounts, but after a while I made it a symlink to /var/run/mtab. It worked OK, AFAIK. Ra?l - 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/