Re: VFAT rename

[H. Peter Anvin]

> 4. POSIX has a bug in dealing with rename("foo","bar") when both foo and
> bar point to the same file. Apparently they wanted to prohibit collapsing
> case (i.e. rename("foo","foo");) and screwed up with wording. Or maybe
> not. Anyway, it's history now.
> 5. #1, #2 and #3 brought us to the situation when rename("foo","Foo")
> triggered a check mandated by #4. They shouldn't - "Foo" should be
> considered negative in that context. Other than that POSIX has nothing to
> this situation - I've misparsed original posting.
> 
> HTH.
>         Al

Let me reiterate: POSIX has *nothing* to do with what happens on a VFAT
filesystem, because a VFAT filesystem (or any other case-insensitive
filesystem) are in blatant violation of POSIX anyway.  Therefore, I
don't see any particular behaviour mandated by POSIX as relevant here
anyway.

	-hpa

-- 
"The user's computer downloads the ActiveX code and simulates a 'Blue
Screen' crash, a generally benign event most users are familiar with
and that would not necessarily arouse suspicions."
-- Security exploit description on http://www.zks.net/p3/how.asp