Mail Archives: cygwin-developers/1999/01/07/17:51:33
Corinna Vinschen wrote:
[...]
> 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.
My original tentative plan was to aim for this:
* There will be two levels of mount points. In order of evaluation:
-- User mount table (from registry, stored in DLL memory).
-- Global mount table (from registry, stored separately in DLL
memory).
By having both types of mounts use the same type of internal
table, we can keep the path code simpler.
* //<drive>/ magic will die a painful death.
* Cygwin DLL will auto-mount '/' into the user (?) mount table if it
isn't in the user or global table. The default will remain the
current system drive.
* Cygwin will automatically add a user mount when converting from a
Win32 path to a POSIX path when there is no user or global mount
point that will work to do the translation. The temporary mount will
use the path /cygdrive/<drive> unless overridden. The temporary
path root could be changed using the "mount" utility.
* mount will get a -remount option that actually works by doing the
umount and mount in one operation. This should fix the bug that
prevents people from reassigning slash.
* getmntent will display mounts in order of evaluation (user mounts,
then global mounts).
I don't want installation of the Cygwin system to require
administrator privs. It seems easy to deal with security issues by
using the registry.
I don't know how I feel about /etc/fstab yet.
--
Geoffrey Noer
noer AT cygnus DOT com
- Raw text -