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 Message-ID: <432F06FB.7A5422B6@dessent.net> Date: Mon, 19 Sep 2005 11:44:11 -0700 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems References: <0IN2009A5RCXL6 AT pmismtp01 DOT mcilink DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Igor Pechtchanski wrote: > OTOH, one of the changes that would be worth making in the managed mount > code is to leave the filename alone unless there's a clash, in which case > the clashing filename becomes encoded. But then any file creation/renaming operation would have to check and see if there was a clash first. That would kill performance. It would also create race conditions, like two processes trying to create clashing files at the same time. > This should work since both NTFS > and FAT are case-preserving filesystems (of course, Cygwin will have to Preserving, yes, but not sensitive. As far as I know it is impossible to make (V)FAT case sensitive, so creating a new file that differs only in case will always fail. NTFS is only case sensitive if you use the Native API, otherwise it is not case sensitive either. I seem to remember a paragraph on MSDN that states this. Even if Cygwin did use the Native API, this would only work for NT with NTFS volumes. 9x/ME has no way to do this, so you're back to encoding filenames anyway. Brian -- 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/