Re: [9fans] FAT32 question

[dexen deVries <dexen.devries@gmail.com>]

On Wednesday 27 of March 2013 08:24:57 Comeau At9Fans wrote:
> I'm mounting a FAT32 flashdrive on a RPi.  However, it seems that some
> sort of legacy 8.3 filename situation is existing.  For instance, if I
> have a directory containing x.c and a23456789.c that the former is
> taken as X.C and the latter is taken as shown.  Therefore, to compile
> x.c is not possible.  So for instance, echo *.c produces a different
> result than echo *.C.  I tried mv'ing the problem files and then back
> but same results.
> 
> I do believe that historically there was some sort of interpretations
> such as this in the evolution from FAT to FAT32, but not sure it
> should be so in current version, or, at least, other operating systems
> don't take this interpretation.  Is there an option or something I'm
> missing?  How do I get to process x.c as x.c and not X.C.


there's no difference between FAT12/16 and FAT32 in treatment of file names, it 
is entirely up to FS driver to create or skip creation of LFN (Long File Name) 
entry, and to use or skip reading an LFN.

every file on FAT has 8.3 name, and may, but does not have to have, an LFN. the 
8.3 name is of limited charset (one of DOS or WINDOWS codepages) and upcase 
only, at least in canonical format. to store lowercase characters, you need 
LFN.

IIRC, some version(s?) of fat drivers on linux did not create LFN for a file 
when the long filename was matching case INsensitive the 8.3 file name, 
essentially leading to loss of character case information.

perhaps something alike is at play here.

-- 
dexen deVries

[[[↓][→]]]


``we, the humanity'' is the greatest experiment we, the humanity, ever 
undertook.