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
Message-ID: <421F6424.FF4AE7D6@dessent.net>
Date: Fri, 25 Feb 2005 09:45:08 -0800
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin preserving filenames ending in period
References: <Pine DOT GSO DOT 4 DOT 50 DOT 0502251705450 DOT 29800-100000 AT argos DOT ee DOT surrey DOT ac DOT uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Lloyd Wood wrote:

> I've just discovered that Cygwin does not preserve filenames ending in
> a period, and treats the filenames with and without the period as
> identical. This is contrary to other linux systems.
> 
> http://www.ee.surrey.ac.uk/Personal/L.Wood/software/SaVi/building-1.2/
> 
> describes the problem; a file named 'Makefile_defs.' was created by
> cvs, but eventually got packaged up as 'Makefile_defs' causing build
> errors on platforms other than Cygwin.

Because It's Windows(tm).  If I recall correctly the lowest level NT
APIs can create filenames with trailing dots on NTFS volumes, but none
of the higher level APIs (win32) can deal with a trailing dot.  The
Microsoft platform SDK in the section "Naming a File" in the Storage
reference says:

"Do not end a file or directory name with a trailing space or a period.
Although the underlying file system may support such names, the
operating system does not. "

I think that Cygwin does use the NT level API for several reasons (speed
and capability), but if it were to allow trailing-dotted filenames it
would mean that you could create a file in Cygwin that would be
undeleteable/unaccessable with normal windows tools.  It would also
create a behavior that would only work on NT kernels and NTFS
filesystem, while Cygwin in general has to support 9x, FAT, etc.

You should look into using a managed mount if you absolutely must have
files with names that are incompatible with Windows.

Brian

--
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/