RE: Setting cygdrive prefix to '/' causes disappearing mounts

[Earnie Boyd <earnie_boyd at yahoo dot com>]

--- Bernard Dautrevaux <Dautrevaux@microprocess.com> wrote:
> 
> For me the patch is OK: being able to explicitely mount things under
> /cygdrive (or whatever it's named) is OK; there was just a misunderstanding
> on what exactly was the cygdrive prefix...
> 

The /cygdrive "prefix" is a pseudo mount point for the unmounted devices.  IMO,
and for the reason this thread exposes, I wouldn't allow access to unmounted
devices.  This would make it more UNIX like.  However, I don't see this
changing as there are benefits to /cygdrive as well.  At the time /cygdrive was
invented I argued that the string should be /umnt to more represent what it's
intent was (besides being shorter) but that suggestion was rejected and
/cygdrive was born.

Now, /cygdrive was invented because the //d convention was getting in the way
of UNC paths.  It caused long delays if the path you referenced didn't exist
locally as you have to wait for the timeout period for each of the domain
servers you have on your network to timeout.

For those of you using the // prefix for unmounted drives I urge you to
reconsider.  Either start using /cygdrive or rename /cygdrive to something more
to your liking such as /umnt but stay away from changing it to //.

Cheers,

=====
--- <http://earniesystems.safeshopper.com> ---
   Earnie Boyd: <mailto:earnie_boyd@yahoo.com>
            __Cygwin: POSIX on Windows__
Cygwin Newbies: <http://gw32.freeyellow.com/>
           __Minimalist GNU for Windows__
    Mingw Home: <http://www.mingw.org/>

__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com