Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Message-ID: <3930FA26.6C57BC6F@vinschen.de> Date: Sun, 28 May 2000 12:51:18 +0200 From: Corinna Vinschen Reply-To: cygwin X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: de, en MIME-Version: 1.0 CC: cygwin@sourceware.cygnus.com Subject: Re: File name syntax (WAS: RE: FW: Can not config sshd) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit It's no general path problem and it's no general $HOME problem. We only have that problem if an application is not enough `defensive' in handling paths. IMHO, it's quite annoying that some applications don't check the given path for trailing slash. That's it, the missing check for trailing slash! Most of the time. I think we should simply do that: - Don't let the root dir be HOME. There's no reason to do so. Tell people that fact as often as they need it (FAQ?). - Let's port applications so that they check the path for trailing slashes as far as it could result in a faulty UNC path (Yes, my openSSH port is affected as well!) Corinna -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com