Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems

[Brian Dessent <brian at dessent dot net>]

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/