On 25/01/22 21:48 Edd Barrett wrote:
>
> > -l Force listing and generation of Windows 95/98 long filenames and
> > separate creation/modification/access dates.
And the next paragraph:
If neither -s nor -l are given, mount_msdos searches the root
directory of the file system to be mounted for any existing
Windows 95/98 long filenames. If no such entries are found, -s
is the default. Otherwise -l is assumed.
> I'm not sure if this is completely accurate. If we were really forcing
> generation of long filenames, then the files `B` and `BBBBB` should have had
> long filename entries, but they didn't appear to.
>
> Should the sentence be suffixed "if the filename doesn't fit in the 8.3
> scheme"? Or perhaps the behaviour `-l` should be changed to *really always*
> create long filenames regardless of the length? I don't know.
The way I read this whole thing is that ``Force'' refers to turning
off the auto-detection and enforce the long mode. See also the
description of the -s flag further down.
> Why do I ask? I need to copy lots of files, preserving case, to an SD card for
> use in an embedded Linux machine on which I don't have control over the
> filesystem type or mount options.
>
> [One hack that I think would work for me, would be to rename all of my files
> lower-case before copying to the FAT filesystem. This would force OpenBSD to
> create long filenames, but that may not be suitable for every user's
> circumstance]
Have you tried enforcing short (old scool) mode by using -s?
tilo
PS: Yes, it's a bit of a mess. But a good part of it comes from
people inventing non-standard ways to fix it, that usually creates
3 problems for one solved.
