Re: Your backup is unsafe!
Roger Gammans (firstname.lastname@example.org)
Thu, 5 Aug 1999 19:25:39 +0100
In article <email@example.com>, Robert de Bath
>On Mon, 2 Aug 1999, Nathan Hand wrote:
>> 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.
>Yes, I thought of this but the coding would be horrific.
If all you want to do is keep a backup/vfat file image intact. How about
a mount option which makes the kernel Vfat filesystem expose VFAT
filenames as sfn:lfn:attrib, or similiar.
If a file is created without the colons -EINVAL is rasied.
Ok so it's not nice but it solves the problems, without multiple dentry
links or other bogosities, Except of course of those filenames which
become unusable. I wouldn't want to traverse this filesystem as a human
but that not necessarily important if its a mount option.
"If I have trouble installing Linux, something is wrong. Very wrong."
-- Linus Torvalds
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/