DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=oYG+AeGhU5qPgSL6
	03jL6I6r6QJqbm+Q+xblMzMjMTzOdme8q9ITJnc0x4kCDwWP0893aa3BTIOmxeDr
	7a4ID/GHime6cXcAtVZTQ7LouSkMlvQO1R6nFYpMQQF6eDLZJWiOUZ4JET4SsX8v
	lHNrdN/n2SWvAS1AMq/JItzPqR0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Sun, 9 Jun 2013 15:43:29 +0400
From: Andrey Repin <anrdaemon@freemail.ru>
Reply-To: Andrey Repin <cygwin@cygwin.com>
Message-ID: <7810384312.20130609154329@mtu-net.ru>
To: Corinna Vinschen <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 1.7.19
In-Reply-To: <20130607141120.GB22187@calimero.vinschen.de>
References: <announce.20130605093949.GA3250@calimero.vinschen.de> <51AF530A.7080306@shaddybaddah.name> <20130605162825.GC3250@calimero.vinschen.de> <CADSoG1u0101m66SbQbNPfW-J4B4o66EyQey2fdrWGy_Bya+1dg@mail.gmail.com> <20130607114015.GC32420@calimero.vinschen.de> <CADSoG1ttmDBbeW_aC2yBqHuKHuxmmLYAYeMpmJB-rSAj4nO8rA@mail.gmail.com> <20130607141120.GB22187@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Corinna Vinschen!

>> I do not think I explained myself properly, sorry: Cygwin would
>> previously read the
>> obcaseinsensitve value under Windows 2000 to emulate the case
>> insensitive behaviour of Windows XP and newer where obcaseinsensitive
>> was present in the registry.
>> 
>> The registry key does not represent the active state of case
>> sensitivity, so it is surely the wrong thing to query and show in
>> cygcheck as it only shows what the state is pending a reboot. Surely
>> it would be better now to query how the case sensitivity actually is
>> here and show that, and get rid of all references to
>> obcaseinsensitive, which is a configuration parameter and private
>> implementation detail of kernel?

> Not from my POV, no.  The registry key is what the user has to change to
> get case sensitive behaviour.

But that setting only permit case-sensitive behavior, but not actually
implement (enable) it.
Actual behavior of case-sensitivity relies on actual support from filesystem,
in case of disk IO operations.
If I read it right, of course.

> We want to know if the user actually changed it in the first place,
> otherwise we can point to that info in case of a case-sensitivity related
> problem.  The active state may be interesting as well, but additionally to
> the registry key info and, as far as I'm concerned, it's a minor problem.

> But, anyway, http://cygwin.com/acronyms/#PTC


--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 09.06.2013, <15:41>

Sorry for my terrible english...


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