cvs.gedasymbols.org/archives/browse.cgi   search  
Mail Archives: cygwin-developers/1999/01/07/16:58:36

From: corinna DOT vinschen AT cityweb DOT de (Corinna Vinschen)
Subject: Re: mount table question
7 Jan 1999 16:58:36 -0800 :
Message-ID: <36954DE3.2F934097.cygnus.cygwin32.developers@cityweb.de>
References: <19990107102740 DOT A30572 AT cygnus DOT com>
Mime-Version: 1.0
To: cygwin32-developers AT cygnus DOT com, Christopher Faylor <cgf AT cygnus DOT com>

Christopher Faylor wrote:
> 
> Geoff is in the process of redoing the handling of Cygwin's mount table.
> We're redesigning the layout of the registry but it occurred to me that
> there was a long-running thread in gnu-win32 where people seemed to be
> advocating for a simple /etc/fstab style file.
> 
> Does anyone have any opinions on this?  Should we drop the registry in
> favor of a file?  Obviously there would have to be at least one entry
> denoting where the root was located but should that be it?
> 
> -chris

I'd like to see it in the following style:

- Use %SYSTEMDRIVE% as default root, text!=binary mounted, if not...

- ...environment variable CYGROOT is set: `CYGROOT=foo', where foo is
  a Windows path, optionally followed by a `/b' for `binary mounted'.

- Important: CYGROOT is only evaluated on first invocation of the dll.

- Usage of /etc/fstab, by convention with \r\n new-line, if not the option
  /b is set in CYGROOT.

- /etc/fstab has to support raw device entries such as the current mount
  table, until the real /dev directory will be used.

This sounds nice to me.

But it's not _really_ necessary. I would also appreciate a solution _with_
registry, if it would be possible, to use only the entries in HKEY_LOCAL_MACHINE
systemwide and disallow the usage of the entries in HKEY_CURRENT_USER.
Moreover, it should then be possible, to edit this entries with `mount/umount'.
This would be a great help.

Regards,
Corinna


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019