Re: VFAT rename

H. Peter Anvin (hpa@transmeta.com)
17 May 1999 01:36:18 GMT

Followup to: <Pine.GSO.4.10.9905160725370.12798-100000@weyl.math.psu.edu>
By author: Alexander Viro <viro@math.psu.edu>
In newsgroup: linux.dev.kernel
>
> On Fri, 14 May 1999, A. Wik wrote:
>
> > It's impossible to rename a file on a VFAT filesystem if
> > the only difference between the old and new names is case
> > (eg. longfilename and LongFilename). The operation is
> > cancelled in fs/namei.c because the lookups return the
> > same dentry for both names. What would be the most
> > reasonable way to fix this?
>
> Get a time machine and go into '89. Then bring a clue to POSIX authors.
> In other words: it's POSIX-mandated behaviour. Bogus, but required.
> It's a feature. That is, an idiotic bug in standard. Nothing to do here.
>

No, it's not. VFAT is not a POSIX-compliant filesystem
(case-insensitivity is explicitly forbidden), so it is not required to
behave that way.

-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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/