DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=OCDvqebOp6Ubn7jIXO3n5t1xGGkIVxCxnH+EWxjQqmL
	pCxFmUCerJwHSBvOHctFcBHuqFPSqq0A9OqEh5Yu6Nl7fZEqC4OURpjFItGzF5jZ
	XNmLjte1++7BfdffGetXCFpf5eu6jL/CZF+y6fFXOKrcLMLRP4pNsv4HPYXvn4AQ
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <51FEB4B1.1080001@tlinx.org>
Date: Sun, 04 Aug 2013 13:08:17 -0700
From: Linda Walsh <cygwin@tlinx.org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Case sensitive filenames for non-NTFS filesystems
References: <51FB56D0.4040609@shaddybaddah.name> <20130802083105.GC18054@calimero.vinschen.de> <51FB7676.6090705@shaddybaddah.name> <51FDBFAD.8060701@tlinx.org> <20130804083150.GF23060@calimero.vinschen.de>
In-Reply-To: <20130804083150.GF23060@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Corinna Vinschen wrote:
> On Aug  3 19:42, Linda Walsh wrote:
>> Shaddy Baddah wrote:
>>> This is the output for L: drive, which is not a physical but logical
>>> volume formatted EXFAT. Hopefully it doesn't alter the
>>> characteristics/attributes. With a bit of extra effort, I could try with
>>> a physical device (format a spare USB stick EXFAT through Windows):
>>>
>>> $ /usr/lib/csih/getVolInfo.exe /cygdrive/l
>> ...
>>> Flags              : 6
>>>  FILE_CASE_SENSITIVE_SEARCH  : FALSE
>>>  FILE_CASE_PRESERVED_NAMES   : TRUE
>>>  FILE_UNICODE_ON_DISK        : TRUE
>> ...
>>
>>> But I have to admit that the "con" of losing case-preservation is a
>>> weighty one. I have discussed in the (very distant) past having issues
>>> with operating on Linux kernel source.
>> ---
>> 	???   Linux preserves and is sensitive to case by default.
>> According to the above, EXFAT does not have a "con" of losing
>> case-preservation.  It *is* case-insensitive just like NTFS.
> 
> No, it isn't.  Did you read the User's Guide?
> http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive
----
It said case was sensitive depending on how you set the KERNEL setting.

so the flags above say CASE_SENSITIVE_SEARCH = false, so my saying
it IS case insensitive just like NTFS -- how is that incorrect?  I'm
confused?

> 
>> Perhaps you are creating files on linux on ex-fat and you have
>> the linux driver setup to be case sensitive?
> 
> You didn't read Shaddy's OP.  He was asking to make ExFAT filenames
> case sensitive *within* Cygwin by adding WCHAR trickery to Cygwin.
----
	But we don't know (or do we?  not sure about what the flags relfect
above) -- if the flag in the kernel was toggled to "case sensitive for all 
subsystem,
wouldn't the above read File Case Sensitive Search=TRUE -- reflecting the kernel
setting?

If they can store case, and one tells the kernel to pay attention to case, wouldn't
it be case sensitive?

???
sorry, don't mean to confuse the issue, but I thought it was the kernel
setting that chose to be sensitive or not.


> That would be possible, of course, as long as the FS is case preserving.
> It's just pretty laborious.
> 
> 
> Corinna
> 

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