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=s42DgSbSQYDuciGloJQFl4FXO232Sx3NgPIncJJJhbQ
	O5fa9rhrP15BMWzfUHs4tJBD65iEKz4F5tHT5ZhkuQbloO64yXXDJ14mSq9v3PUi
	bVDOp87dcWuX+hm6TSIlg8rVszApaVB0pibdX0KwAvEGejOCCpgfO7ZcgirrFbNc
	=
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=sbvgWCGm+lTrRKf78YtiQWh1OAI=; b=h4kcC84mXIqSZUklh
	25jPraBrNX8dLuB6borc4CijQBWgvNNksrkByfF43ZrPuw03C8vHYoWrDiJtFB5L
	HUmsJHsrBv5oF6k93JQyqcoDOgJsMZaB31xKq/GbSW9NPtvdM1INtzx+ZUIiRoQl
	Pj8Ai8GtVY2XwNflrBf39E9s1c=
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:	<51FB7676.6090705@shaddybaddah.name>
Date:	Fri, 02 Aug 2013 19:05:58 +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>
In-Reply-To:	<20130802083105.GC18054@calimero.vinschen.de>
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=cvPdL9u0RiqYejDjeyUA:9 a=QEXdDO2ut3YA:10

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. I have discussed in the (very distant) past having issues
with operating on Linux kernel source. I haven't done so in quite a
while, but in the past there seemed to be many places where there
were filename collisions due to not being able to preserve case.

It may not have been the Linux kernel, but I remember one crazy source
package where I struggled to find correct information because they had
a INSTALL.TXT and an Install.txt (or something like that).

-- 
Regards,
Shaddy
of the Linux



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

- Raw text -