Re: CONFIG_VFAT_FS_DUALNAMES regressions

[Jamie Lokier <jamie@shareable.org>]

David Newall wrote:
> tridge@samba.org wrote:
> > Hi Jan,
> >
> >  >  * "cp dscf4160.jpg dscF3011.jpg" does not work - i.e. cam ignores the
> >  >    file without error.
> >  >    Reason for that is that dscF3011 has an illegal 8.3 name
> >
> > yep, that's expected. I suggested a possible way of handling this to
> > Hirofumi-san (ie. change the case of the name), but he prefers to keep
> > things simple for now.
> >   
> 
> Expected or not, it's a serious bug. If it doesn't canonify the
> filename, it should return an error. Lying by returning success is
> horridly wrong. And I might just suggest that as people are now
> accustomed to typing mixed-case filenames, it's a bug that's likely to
> occur more frequently than it might at first seem.

It's no different from writing a long name, though, is it?

"cp dscf4160.jpg dscf3011.jpeg" would also be ignored by the
camera, because there is no corresponding 8.3 file name.

It's a bit clearer when mounted with shortname=winnt or
shortname=mixed, because then I'd expect files created by the camera
to show as upper case in Linux, and it would be obvious that you might
have to create new files for the camera that look the same as the camera's.

The current Linux default shows 8.3 short-name files in lower case
(i.e. pure FAT shows as lower case), but files created in Linux with
8.3 lower case names create a long name.  Which is bound to cause some
confusion.

I agree with tridge, shortname=winnt makes sense when dualnames are off.

Unfortunately it doesn't preserve case when creating in Linux and
reading in Windows 95/98/ME and devices with a similar implementation.

For that reason, shortname=mixed is better when dualnames are on.

-- Jamie