X-Spam-Check-By: sourceware.org
Message-ID: <447420E3.5B3609B3@dessent.net>
Date: Wed, 24 May 2006 02:01:23 -0700
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Handling special characters (\/:*?"<>|) gracefully
References: <2ED63F31975E1E428B3732A68923F480ECA6FC AT rain DOT scur DOT com> <e4vn30$s0a$1 AT sea DOT gmane DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
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

mwoehlke wrote:

> (Speaking of case sensitivity, is it a Windows limitation that Cygwin
> can't do this? I'm pretty sure it isn't an NTFS limitation, as Interix
> has true case-sensitivity.)

As I understand it, the win32 API preserves case but is not case
sensitive.  The native API is both, so in theory an application that
used only native calls could cope with both README and Readme, but no
win32 app could.  So, from the standpoint of Cygwin this is pretty
useless as A) it would take significant code rewrites to use the native
API everywhere (not to mention backcompat hell for 9x/ME) and B) it
would lead to the situation (which we briefly got a taste of somewhere
in a past 1.5.x release) where Cygwin was able to create files that
could not be deleted by Explorer or any other regular Windows app.

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/