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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=TbvnPVZ6wXJZJpaFB7iBJXMb+zGAIS6MfKSru7TzJtj
	EdFU4J7IDXCpokgH2MvX+79JpsZfkDbaVB7Bl05DfcXZCalFwYhYL6E2mcmP7yjc
	34GvaEEVq8uIfFzdsEzub48x7pVGC/KIhNvf34zeAo1XcJaTujgYIN3R59mFvSP4
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=sr6x9x4jTLwjPZdfuiCCk4810Ao=; b=t7N2sqZKWs8EwZnuK
	YR4IkdBJOlTGQgeBr95gHnTxOemxCnUSu4Dsat55leHTkyE+grtGPuX9N68tPuLt
	jQ3X3S07gq5p5gK73sJSgYyysREResFwrrL/4aRrv3r/KiPG5MpHsNZay3C5c/Dj
	7KklNqTMPg1mgG4rhoadSnA2G0=
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.6 required=5.0 tests=AWL,BAYES_50,KHOP_THREADED,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,RCVD_VIA_APNIC,RDNS_NONE autolearn=no version=3.3.1
Message-ID: <51FC549E.7000603@shaddybaddah.name>
Date: Sat, 03 Aug 2013 10:53:50 +1000
From: Shaddy Baddah <lithium-cygwin AT shaddybaddah DOT name>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130704 Icedove/17.0.7
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Case sensitive filenames for non-NTFS filesystems
References: <51FB56D0 DOT 4040609 AT shaddybaddah DOT name> <20130802083105 DOT GC18054 AT calimero DOT vinschen DOT de> <51FB7676 DOT 6090705 AT shaddybaddah DOT name> <20130802102958 DOT GD4166 AT calimero DOT vinschen DOT de>
In-Reply-To: <20130802102958.GD4166@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Optus-CM-Score: 0
X-Optus-CM-Analysis: v=2.1 cv=YYGEuWhf c=1 sm=1 tr=0	a=RkPObcNqpdaXDoCDBSw5Xw==:117 a=RkPObcNqpdaXDoCDBSw5Xw==:17	a=PO7r1zJSAAAA:8 a=fUdQyOyA9-cA:10 a=KjPW4OQsgTQA:10 a=IkcTkHD0fZMA:10	a=Yw4-dFCx6oUA:10 a=KG5MlycN0YTrnBLLAswA:9 a=QEXdDO2ut3YA:10

Hi,

On 02 Aug 2013 20:29+1000, Corinna Vinschen wrote:
> On Aug  2 19:05, Shaddy Baddah wrote:
>> Hi,
>>
>> On 02 Aug 2013 18:31+1000, Corinna Vinschen wrote:
>>> Correction, not only NTFS.  Here's the source code comment:
>>
>> Sorry, yes I forgot that it was coded to let Windows make the decision.
>>
>>>> Unfortunately, in providing EXFAT, Microsoft has not seen fit to carry
>>>> over the same handling in the kernel as it does in NTFS.
>>>
>>> ExFAT is based on FAT/FAT32, so it's understandable.  I don't have ExFAT
>>> available.  Assuming your ExFAT drive is drive X:, can you please show
>>> me the output of
>>>
>>>    /usr/lib/csih/getVolInfo.exe /cygdrive/x
>>>
>>> If it returns different values than FAT, it might be worth to handle
>>> specificially in Cygwin's mount code.
>>
>> 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
>> Device Type        : 7
>> Characteristics    : 121
>> Volume Name        : <>
>> Serial Number      : 1211155165
>> Max Filenamelength : 255
>> Filesystemname     : <exFAT>
>> Flags              : 6
>>    FILE_CASE_SENSITIVE_SEARCH  : FALSE
>>    FILE_CASE_PRESERVED_NAMES   : TRUE
>>    FILE_UNICODE_ON_DISK        : TRUE
>>    FILE_PERSISTENT_ACLS        : FALSE
>>    FILE_FILE_COMPRESSION       : FALSE
>>    FILE_VOLUME_QUOTAS          : FALSE
>>    FILE_SUPPORTS_SPARSE_FILES  : FALSE
>>    FILE_SUPPORTS_REPARSE_POINTS: FALSE
>>    FILE_SUPPORTS_REMOTE_STORAGE: FALSE
>>    FILE_VOLUME_IS_COMPRESSED   : FALSE
>>    FILE_SUPPORTS_OBJECT_IDS    : FALSE
>>    FILE_SUPPORTS_ENCRYPTION    : FALSE
>>    FILE_NAMED_STREAMS          : FALSE
>>    FILE_READ_ONLY_VOLUME       : FALSE
>>    FILE_SEQUENTIAL_WRITE_ONCE  : FALSE
>>    FILE_SUPPORTS_TRANSACTIONS  : FALSE
>>
>>> Well, from my POV, yes.  It doesn't make sense to use ExFAT for serious
>>> work anyway, it's for SD cards and stuff like that.
>>
>> I understand that. It's just that after years of being frustrated with
>> moving files around various NTFS partitions and fighting with
>> ownership/permission issues, especially where Cygwin work
>> files/directories are involved, I've decided that I should PoC a brave
>> new world.
>>
>> That being giving up on security through file/folder ACLs, and just
>> mount FAT32 (or the candidate EXFAT) fs via as an encrypted logical
>> volume.
>>
>> My Cygwin work will be access that way. If I need to move it, I move
>> the encrypted file only.
>>
>> But I have to admit that the "con" of losing case-preservation is a
>> weighty one. [...]
>
> Giving up on security but wanting case sensitivity... so why not use
> NTFS with the noacl mount option where necessary?

To be honest, my bug bear with NTFS has been the file/folder ownership.

But I think noacl's is probably the best compromise for general NTFS
ACL issues.

-- 
Thanks,
Shaddy

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