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 Message-Id: <4.3.1.2.20000527122319.00b7ea30@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Sat, 27 May 2000 12:27:19 -0400 To: "Parker, Ron" , "cygwin AT sourceware DOT cygnus DOT com" From: "Larry Hall (RFK Partners, Inc)" Subject: RE: File name syntax (WAS: RE: FW: Can not config sshd) In-Reply-To: <200005262126.RAA23411@acestes-fe0.ultra.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 05:22 PM 5/26/00, Parker, Ron wrote: > > 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. Actually, I should have said "////" to be clear. I guess as long as the NFS style syntax was supported by Cygwin and was supported in all places that the current UNC paths are supported in Windows (i.e. *everywhere*), there shouldn't be any loss of functionality with this change... Larry -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com