X-Spam-Check-By: sourceware.org Message-ID: <46CC940F.7080408@x-ray.at> Date: Wed, 22 Aug 2007 21:52:47 +0200 From: Reini Urban User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] Updated [experimental]: coreutils-6.9-5 References: <46CB58A1 DOT 3040202 AT x-ray DOT at> <46CB5D57 DOT 5080401 AT byu DOT net> <20070822083015 DOT GA13475 AT calimero DOT vinschen DOT de> In-Reply-To: <20070822083015.GA13475@calimero.vinschen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Corinna Vinschen schrieb: > So, in the Linux/FAT example we have a case-sensitive OS with a > case-insensitive FS, with Win32/NTFS (Cygwin/NTFS) we have a > case-insensitive OS with a case-sensitive FS. While the NT kernel can > return information about the case-sensitivity of the underlying FS (***) > (****), I don't know about other OSes. BTW, I just improved the perl API concerning Win32 case-tolerance. perldoc File::Spec Cygwin Cygwin case-tolerance depends on managed mount settings and as with MsWin32 on GetVolumeInformation() ouFsFlags == FS_CASE_SENSITIVE, indicating the case significance when comparing file specifications. Default: 1 MsWin32 MSWin32 case-tolerance depends on GetVolumeInformation() ouFsFlags == FS_CASE_SENSITIVE, indicating the case significance when comparing file specifications. Since XP FS_CASE_SENSITIVE is effectively disabled for the NT subsubsystem. See http://cygwin.com/ml/cygwin/2007-07/msg00891.html Default: 1 Interestingly: Epoc, VMS, OS2 and Mac are all case tolerant, too. > So we're back to fpathconf(_PC_CASE_INSENSITIVE): It appears that > case-insensitive operation on the POSIX application level depends on > such a flag. I'm also planning to allow case-sensitive operation on > NTFS in Cygwin at one point, which would make this flag necessary as > well. I don't think it would ever become part of the POSIX standard, > though. > > > Corinna > > > > (*) In theory, Cygwin's rename could do the same and still move within > POSIX rules, no matter how frustrating this behaviour might be. > > (**) Plus a registry setting since XP. > > (***) See the FILE_CASE_SENSITIVE_SEARCH file system flag: > http://cygwin.com/ml/cygwin/2007-08/msg00013.html > > (****) As far as the underlying FS returns the correct flags, of course. -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/