John R Pierce wrote:
Ross S. W. Walker wrote:
How about a FUSE file system (userland, ie NTFS 3G) that layers on top of any file system that supports hard links, intercepts the FS API and stores all files in a hidden directory and names them after their MD5 hash and hard links to the file name in the user directory stucture. When the # of links drops to 1 then the hash is removed, when new files are copied in if the hash collides with an existing one the data is discarded and only a hard link is made.
Of course it will be a little more involved then this, but the idea is to keep it really simple so it's less likely to break.
yeah, be REAL fun when an app random updates one of said files.
Yes, but as the writer of the FUSE file system you can make it inaccessible to apps.
-Ross
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.