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 X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Fri, 6 Sep 2002 13:41:19 -0400 (EDT) From: Igor Pechtchanski To: cygwin-developers AT cygwin DOT com Subject: Re: Contemplating drastic change to mount handling In-Reply-To: <20020906161934.GJ21699@redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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. > cgf /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?). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! It took the computational power of three Commodore 64s to fly to the moon. It takes a 486 to run Windows 95. Something is wrong here. -- SC sig file