> The problem isn't straightforward. Simply stated, VFAT has two names for
> a file, both are valid, both must be preserved, only one is visible, but
> both are usable at all times. This does not map onto any UNIX filesystem
> so some magic is needed.
Under _Windows_ both are valid. Do you really think this brain dammage
should be kept in Linux? There is no reason for the short name to be
visable _except_ when there are interactions with DOS, this comes down
to dosemu, samba and backups.
> How about a magic file in each VFAT directory which contains mappings of
> long to short filenames. You only see the long names using standard UNIX
> file I/O. Then backups work, because you backup the magic file too, so a
> restore will put the correct short/long mappings back.
Yes, I thought of this but the coding would be horrific. I think this would
work out to be just the same as using a directory by directory sfn_backup,
and IMO it's better to do it in userspace and keep those horrors from the
kernel.
> Nathan Hand - Chirp Web Design - http://www.chirp.com.au/ - $e^{i\pi}+1 = 0$
> Phone: +61 2 6230 1871 Fax: +61 2 6230 1515 E-mail: nathanh@chirp.com.au
--
Rob. (Robert de Bath <http://poboxes.com/rdebath>)
<rdebath @ poboxes.com> <http://www.cix.co.uk/~mayday>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/