Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: "Parker, Ron" To: "Larry Hall (RFK Partners, Inc)" , "Parker, Ron" , "cygwin AT sourceware DOT cygnus DOT com" Subject: RE: File name syntax (WAS: RE: FW: Can not config sshd) Date: Fri, 26 May 2000 16:22:28 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01BFC758.F8E0365A" Message-Id: <20000526212550.5941CF802@mx1.hotpop.com> ------_=_NextPart_000_01BFC758.F8E0365A Content-Type: text/plain; charset="windows-1252" > Right. The significance is for UNC paths which can be easily > access currently > using "///" in Cygwin now... Understood. My intention was that server:share would be converted to \\server\share before it reached the Windows file API's used inside of cygwin. The entire idea was that many UNIX programs parse the colon paths as network paths already and this would bring cygwin a little more inline with the UNIX world. ------_=_NextPart_000_01BFC758.F8E0365A Content-Type: text/plain; charset=us-ascii -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com ------_=_NextPart_000_01BFC758.F8E0365A--