Re: Linux 2.2.11pre2 proposed patch

Frank =?iso-8859-1?Q?Matthie=DF?= (Frank.Matthiess@t-online.de)
Tue, 20 Jul 1999 23:59:13 +0200

Craig Milo Rogers schrieb:
>
> The natural place to put the inode map would be on the same
> underlying FAT filesystem, but for extra brownie points you could
> perhaps arrange for it to be located on a different filesystem. To
> protect against external meddling (e.g., renaming a file with
> Ms. Windows), the persistent inode map should contain checksums of
> the VFAT filesystem's underlying directory pages.

As i know, the (v)fat is organize in clusters. This clusters can be identified
by numbers. It's just an idea, but i think it's possible to 'map' this number
to inode number, because, they are 16/32bit long. At this way there is no
problem with changing inode number between reboots.

Is it a bad idea ?

> This is piling cruft upon cruft, but it could be made to work
> under the given constraint. It could even be yet another layered
> filesystem (PVFAT?) in the towering FAT ensemble. Future generations
> will not thank you, though.

-- 
Frank Matthieß	      


Privat Frank.Matthiess@GMX.net			                +49-5245-4662
Firma  Frank.Matthiess@decor-metall.de                       +49-5222-286-315


-
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/