Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
From: "Gerald S. Williams" <gsw AT agere DOT com>
To: <cygwin-developers AT cygwin DOT com>
Subject: RE: True case-sensitive filenames
Date: Mon, 20 Jan 2003 10:10:06 -0500
Message-ID: <GBEGLOMMCLDACBPKDIHFEEOGDAAA.gsw@agere.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030120100052.GD21587@cygbert.vinschen.de>

Corinna Vinschen wrote:
> On Fri, Jan 17, 2003 at 05:35:57PM -0500, Earnie Boyd wrote:
> > IIRC, there is a CYGWIN variable option for this already.
> 
> No, there isn't.  Sergey had a patch relative to b18 or b19 once but
> it never made it into the Cygwin source.

This is encouraging. So I guess there is interest in adding a
flag like that. If so, I'll look into it some more.

If the fhandler_disk_file class used for all disk file accesses,
the change could be limited to just fhandler_disk_file::open().
It may make sense to extend fhandler_base with a way to support
case-sensitive opens and use that instead, though.

Does anyone know of any alternative file access mechanisms that
might cause problems? SETUP might be an issue (it's compiled
with mingw, right?), but we can cross that bridge later.

-Jerry