Re: Error with managed mount point.

On Wed, 15 Dec 2004 19:21:51 -0500, Larry Hall wrote: 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. No, they need to be removed. Windows behavior is to ignore one or more

RE: Error with managed mount point.

-Original Message- From: cygwin-owner On Behalf Of Mark Paulus Sent: 16 December 2004 14:32 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

Error with managed mount point.

Hi, If someone can point me to the proper place, I would be willing to further analyze this, but this is the issue: Files/Directories that end in a '.'(dot) are not retaining the dot. For example: I am attempting to untar a tarball that contains this (done on a linux box) drwxr-xr-x 22

Re: Error with managed mount point.

At 02:06 PM 12/15/2004, you wrote: Hi, If someone can point me to the proper place, I would be willing to further analyze this, but this is the issue: Files/Directories that end in a '.'(dot) are not retaining the dot. For example: I am attempting to untar a tarball that contains this (done on

Re: Error with managed mount point.

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

Re: Error with managed mount point.

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,