In retrospect I have to agree. It's clearly better to only show the long
filenames and have special "VFAT aware" programs to handle backups. This
can be done via ioctl, a /proc interface, etc. It's a robust solution.
> > 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.
Yes, I agree. The existing Linux VFAT filesystem is clean, UNIX-like, it
hides the major braindamages, and it fails in very few cases. Far better
to solve specific problems (like VFAT backups) with specialised tools.
--
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
-
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/