Mail Archives: cygwin/2001/09/26/11:34:11
"Larry Hall (RFK Partners, Inc)" wrote:
>
> At 10:44 AM 9/26/2001, Keith Starsmeare wrote:
> >I just updated a colleagues cygwin and couldn't immediately figure out why
> >it was going so very slowly. The reason - //c references in the path. Every
> >time a command was issued that searched past that reference it would freeze
> >because it now scans the network. Ouch!
> >
> >Also, this opens the (remote) possibility of unscrupulous, twisted people
> >calling their machines 'C' to catch people out!
> >
> >I guess we knew this was going to happen, but I wish that there was a way to
> >temporarily issue some kind of big, unmissable warning somewhere! (But I'm
> >not volunteering, I can't think of where would be the best place - setup,
> >bash maybe?)
>
> The problems you state are exactly the reasons for removing this syntax
> for accessing drives. It's too dangerous and problematic.
In case it wasn't clear from Larry's message, the '//c' syntax for
accessing local drives was deprecated for the past year, and has been
removed completely beginning with cygwin-1.3.3. Therefore, '//c' now
has the single, non-ambiguous meaning of 'go look at the machine named
"C"'. (ergo, if you want to avoid network delays, don't use '//'
notation. To access local drives, the only mechanisms are now:
/cygdrive/c/ or 'mount C: /c')
--Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -