lkml.org 
[lkml]   [1999]   [Aug]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Your backup is unsafe!
In article <5ef05fb67d27bfeb@home-box.demon.co.uk>, Robert de Bath
<rd103979@home-box.demon.co.uk> writes
>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.
[snip]
>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.

TTFN
--
Roger Gammans
"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 majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:53    [W:0.290 / U:0.988 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site