Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.2.0.14.0.20041215191317.05297008@pop.prospeed.net>
Date: Wed, 15 Dec 2004 19:21:51 -0500
To: Mark Paulus <mark DOT paulus AT mci DOT com>, "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
From: Larry Hall <lh-no-personal-replies-please AT cygwin DOT com>
Subject: Re: Error with managed mount point.
In-Reply-To: <0I8S00B6J75MEI@pmismtp01.mcilink.com>
References: <0I8S00F9L2FIAT AT pmismtp02 DOT mcilink DOT com> <0I8S00B6J75MEI AT pmismtp01 DOT mcilink DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 03:48 PM 12/15/2004, you wrote:
>Running strace pointed me to the proper place to look
>for the error.
>
>However, the proper fix is maybe more of a philosophy
>issue.  
>
>I found some code in path.cc that removes trailing dots and
>spaces from a file name in path_conv::check().  The question is,
>should these trailing spaces/dots actually be removed, or should
>they be converted to %20/%2E, only if they are part of the file/
>directory name?  Or, should they be stripped for ALL file searches,
>so that something like /foo./bar will be found under the windows
>path /%66oo/%62ar?


No, they need to be removed.  Windows behavior is to ignore one or more
'.'s at the end of a file so we're stuck with that in normal Cygwin-working
mode.  I actually haven't delved into the inner workings of the managed 
mount option code but if there's going to be a place to hang onto and 
translate the trailing '.'s, it would be in this special case code.  Without
looking at more than just the patch lines, I'm guessing that the patch you 
made (submitted to the Cygwin patches list) to path_conv::check() are
going to be in too generic of a spot to be the right thing to do for just
managed mount mode, though I could be wrong.  I'll try to find a minute 
tonight to comment further.
 

--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/