Mail Archives: cygwin-developers/2001/05/23/23:46:39
On Wed, May 23, 2001 at 06:28:02PM -0400, Earnie Boyd wrote:
>Christopher Faylor wrote:
>>
>> I am thinking of taking the drastic step of getting rid of //c?
>>
>
>Yeah!!!
>
>> Any comments on this? Should we just make it configurable with
>> a cygwin option:
>>
>> set cygwin=deprecated_drive_access
>>
>> ?
>>
>
>No. How about changing the value of CYGWIN_INFO_CYGDRIVE_DEFAULT_PREFIX
>to `/'?
I've never been a fan of changing the default to '/' so, there's the first
hurdle.
The second hurdle is the one of causing complete and total confusion for
everyone who uses the new release. They wouldn't be able to use //c and,
if they were aware of /cygdrive/c, they wouldn't be able to use that either.
So, I'm definitely not going to do this.
In other words:
YES:
Q: Why did you get rid of //c? It seemed to be working fine.
A: //c was an ill-advised way of accessing local drives in Cygwin.
Cygwin's previous use of // conflicted with the mechanism that Windows
used to access remote "shares". This meant that you could never access
a share named //a, //b, //c, etc. under Cygwin.
NO:
Q: Why can't I access my /c directory? It seemed to be working fine before.
A: Because we thought that it would be more likely that you'd have a
share named c than a directory named c?
cgf
- Raw text -