X-Recipient: archive-cygwin AT delorie DOT com
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:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=XwNwQxLGPWPmkHcQWUgTmhOw4C0wFBrxFOYOik5mAZxJKIHZnPsqW
	vFcv12g/vGoUtKRepmyhHIstoRfYB39qX4mxTnz1OkeY3RH84qbRX6MdKped+8na
	yr/XvO0wKAEQEP1qaRn9PP330TBiXeaVU2vTjbY4a9O30SMCqyB7U4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=hETj9Ea41ByatLb/Pf73wPs6AG4=; b=mrDNOI1wXbAnF6M9+eFZpzs0FQFE
	hUkWPb21EUnJ5HDaS5KBwzFd8bqlT2P5LZU5xpw8GybPIqfGWk6PwrAIYhkvtfP4
	W67b9HfCw7S/ODVf8Kl6vvHTB6pzqadjWK6aUaJCy7UY3X2cpx1sob4rlxVTG/Yo
	eb6ZET7PoWJxzUs=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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
X-Spam-SWARE-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_20,RDNS_NONE autolearn=no version=3.3.1
Date: Mon, 5 Aug 2013 10:12:12 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Case sensitive filenames for non-NTFS filesystems
Message-ID: <20130805081212.GI23060@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <51FB56D0 DOT 4040609 AT shaddybaddah DOT name> <20130802083105 DOT GC18054 AT calimero DOT vinschen DOT de> <51FB7676 DOT 6090705 AT shaddybaddah DOT name> <51FDBFAD DOT 8060701 AT tlinx DOT org> <20130804083150 DOT GF23060 AT calimero DOT vinschen DOT de> <51FEB4B1 DOT 1080001 AT tlinx DOT org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <51FEB4B1.1080001@tlinx.org>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Aug  4 13:08, Linda Walsh wrote:
> 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?

Yes.  You just make assumptions rather then checking the facts.
FILE_CASE_SENSITIVE_SEARCH is TRUE on NTFS.

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

The OS handles that in three stages, Cygwin adds one:

- FILE_CASE_SENSITIVE_SEARCH == TRUE

  The filesystem itself is casesensitive.  This is set on NTFS, but not
  on {ex}FAT{32}.  So file operations on NTFS *can* be casesensitive,
  but they can't on FAT.

- The CreateFile/NtCreateFile calls have flags which handle case
  sensitivity.  The default for CreateFile is caseinsensitive, unless
  the FILE_FLAG_POSIX_SEMANTICS is used.  The default for NtCreateFile
  is casesensitive, unless the OBJECT_ATTRIBUTE contains the
  OBJ_CASE_INSENSITIVE flag.

- Starting with XP, the kernel supports a global setting, set by the
  registry key mentioned in the user's guide.  If the obcaseinsensitive
  registry value is set to 1, which is default since XP, all of the
  above is simply ignored.

- Cygwin only:  Mount flag "posix=1" is default, so casesensitivity
  is default, unless
  - the obcaseinsensitive registry value is 1,
  - the filesystem has FILE_CASE_SENSITIVE_SEARCH == FALSE,
  - the mount point is explicitely mounted with "posix=0",
  - the incoming path is a DOS path (drive letter, backslashes).


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

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