Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Thu, 22 Jul 2004 22:46:44 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Slight problem with case sensitivity on managed mounts with C VS-1.11.6 Message-ID: <20040722204644.GZ11473@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Jul 22 18:30, Dave Korn wrote: > No it isn't. NTFS is case *preserving*; neither NTFS nor windoze are case > *sensitive*. That's only half the truth, though... > I am right that using the //./ notation invokes the NtCreateFile function, > aren't I? I think that's why the syntax works for deleting NUL files and so > on, so it ought to work in this case too, shouldn't it? Nope. It has nothing to do with using NtCreateFile instead of CreateFile. The difference between case preserving and cas sensitive is caused by giving a specific flag to either function: FILE_FLAG_POSIX_SEMANTICS. Needless to say that this only works on file systems supporting case sensitivity. NTFS is such a file system, btw. FAT on the other hand... The problem in using FILE_FLAG_POSIX_SEMANTICS is this: Any other application which doesn't use that flag might get seriously confused by having two files which only differ in case. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/