From: huott AT pinebush DOT com (Ed Huott)
Subject: Re: UNC path syntax
2 Apr 1997 00:44:29 -0800
Sender: daemon AT cygnus DOT com
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <199704020248.VAA03095.cygnus.gnu-win32@sol.pinebush.com>
Original-To: Jim Balter <jqb AT netcom DOT com>
Original-cc: Tom Yonkman <tyonkman AT elementalsoftware DOT com>, gnu-win32 AT cygnus DOT com
In-reply-to: Your message of "Tue, 01 Apr 1997 16:24:46 PST."
             <3341A74E DOT 627F AT netcom DOT com> 
Original-Sender: owner-gnu-win32 AT cygnus DOT com

In message <3341A74E DOT 627F AT netcom DOT com>, Jim Balter writes:
>You can refer to UNC paths with, e.g., "\\xxx\y", but not
>"//xxx/y", which gets turned into "c:\xxx\y".  You can use names like

Are you sure about this?  With my (unpatched) copy of b17.1 running on
NT 3.51 or NT 4.0, cygwin's `ls' command fails when I use this syntax.
E.g.:

  C:\>ls \\newt\c
  ls: \\newt\c: No such file or directory

where "\\newt\c" is a valid share name on my network (i.e. I can do
`dir \\newt\c' and it works).

BTW, the behavior of `ls' invoked under bash is the same (with all \'s
properly escaped or quoted, of course! :-).  Please let me know if
there's something I'm missing here.

<ED>
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".