Message-Id: <200005301721.NAA25468@delorie.com> 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: cygwin Subject: RE: File name syntax (WAS: RE: FW: Can not config sshd) Date: Tue, 30 May 2000 12:18:05 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01BFCA5B.62CFC422" ------_=_NextPart_000_01BFCA5B.62CFC422 Content-Type: text/plain; charset="windows-1252" I would like to thank Chris for finding the reference in the Single UNIX Spec. where //path is implementation defined, Bob McGowan for his fine job of summarizing what started this whole thing, and everyone else for their input. Also I would like to apologize for setting off a match in a dry field with this topic. I did not intend to fill everyone's mailboxes over the long holiday weekend in the US. I did originally ask the question because I was concerned that there might be things I was not considering. I will not be working up the previously mentioned patch. While it might solve some problems it is obvious that it would introduce more problems than it would cure. ------_=_NextPart_000_01BFCA5B.62CFC422 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_01BFCA5B.62CFC422--