Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Fri, 6 Sep 2002 17:00:52 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: Contemplating drastic change to mount handling Message-ID: <20020906210052.GA26002@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <20020906161934 DOT GJ21699 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i On Fri, Sep 06, 2002 at 01:41:19PM -0400, Igor Pechtchanski wrote: >On Fri, 6 Sep 2002, Christopher Faylor wrote: > >> On Fri, Sep 06, 2002 at 01:58:54PM +0200, Corinna Vinschen wrote: >> >> /etc/fstab would be the same as it is on linux. /etc/mtab would be a >> >> binary (trie) representation of the mount table which could be mapped >> >> into cygwin on the fly, eliminating the need to parse any options. >> >> >> >> So, basically the "permanent" mounts would be whatever existed in >> >> /etc/fstab, maybe with an auto field turned on. >> > >> >And getting rid of user mounts... :-) >> >> I don't know if we can go that far. I think that some people still >> need them. > >/proc/mounts might be a good location for the trie, to mimic Linux usage. >Then /etc/mtab can store all mounts as text (the info that's currently in >the registry), and /etc/fstab would only have permanent mounts (currently >system?). The trie is an actual file so it can't really reside in /proc/mounts. It really resembles /etc/mtab more than /proc/mounts in this regard. cgf