Hi Jan,
 > The mount(8) manpage becomes pretty ambiguous with the dualnames

 > patch.
yes, the man page will need an update certainly. 
 > Making WINNT the default would cause many a `ls` output to just

 > scream at me in uppercaps because there are programs that

 > create long names with all-uppers.
well, you could also argue that having WINNT in effect does the

'correct' thing. It causes ls to display the name that is actually in

the filesystem. 
I think the current default for VFAT on Linux is rather misleading. It

always displays 8.3 names as lowercase, so MAIL.dat, foo.TXT and other

combinations always display as lowercase, regardless of what the

application that created the file chose for the name.
With the winnt option the names are shown as the application that

created them chose. That is also what all current versions of Windows

do as far as I know.
yes, this means that for a digital camera card, where the camera is

always choosing all uppercase for the filenames, it can look like

'shouting' on a Linux system where lowercase is more usual. It is

however an accurate representation and maximises compatibility.
I think the current defaults were chosen a long time ago, when Win95

was more the norm, and 16 bit apps that weren't written for case

preserving filesystems were common. That era is long gone.
 > shortname really needs to be split into "shortname that is applied

 > during creation" and "shortname that is applied upon readdir".
perhaps, but I think (as you discovered!) the current VFAT options are

already too complex, and very few people set them correctly. Adding

more options to get yet more varients to the case handling behaviour

doesn't seem like a good move to me.
Other OSes with FAT implementations just choose a sane default (which

probably matches our shortname=winnt pretty closely) and the user

never gets to choose. Choice isn't always a good thing!
I should also point out that if we followed Alan's reasoning then we'd

have to actually make all these options separate filesystems, and we'd

only be able to call the shortname=winnt one "VFAT" as that is the

only one that matches Windows behaviour. The others all treat the

filesystem differently to what Windows does. (no, I'm not seriously

proposing this, just pointing out that the "it has to be a different

filesystem name" has not been always applied previously).
I wonder if Pavel still thinks that VFAT was perfect before I came

along :-)
Cheers, Tridge

--

To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in

the body of a message to majordomo@vger.kernel.org

More majordomo info at  http://vger.kernel.org/majordomo-info.html