Re: VFAT kernel considerations

[Julian Reschke-FJR010 <Julian_Reschke-FJR010@email.mot.com>]

q-funk@megacom.net%INTERNET wrote:
> 
> After playing around with 1.15.b2 for about a week, a few things
> just popped into mind:
> 
> 1) Docs recommend trying VFAT on the boot drive.
> 
>    I have reservations about that. Basically, I consider partition
>    assignment following this scheme:
> 
>    A: VFAT
>    B: disabled (toggle_B) or favorite FS (VFAT, Minix, Ext2, ...)
>    C: TOSFS
>  D-Z: favorite FS (VFAT, Minix, Ext2, ...)
> 
>    The problem I have with completely eliminating TOSFS is because
>    I consider C: as a "compatibility" partition.  Several old apps
>    implicitely expect finding FILENAME.EXT even though filename.ext
>    should be acceptable, because the code uses uppercase filenames.
> 
>    Some recent example of this is NEWSie, which passes an uppercase
>    filename to the text editor, but writes using lowercase to disk,
>    hence neither qed nor everest would find the file, if using VFAT
>    or Minix partitions for NEWSie's temp dir...
> 
>    Therefore, I strongly recommend keeping C: as TOSFS only.

VFAT is a case preserving file system (at least it should be :-). This
means, that a program can open FILENAME.EXT even if it has been
created as filename.ext.

If this really is not yet the case, it needs to be put onto the
todo list :-)

Regards, jr