> OE>> storage of just one instance is something else. If you just symlink
> OE>> some files to a single file, and the owner of that file deletes it,
> OE>> you're screwed. What this thingy does is take care of all of that (again,
>
> Hardlink?
What most of you are missing in your zealotness is that the discussed
service is based on reparse points, a new technology in Windows 2000.
I'm not a Windows guy, but the way I understand it is that a reparse
point is a new file attribute which allows you to associate a kernel
module with that file, so that this module is called when that file
is accessed. Reparse points are also used by Microsoft in e.g. their
distributed filesystem.
This is a MUCH cleaner solution than using kernel modules that trap
file-related system calls. It also, by design, allows several such
modules to be loaded concurrently.
I couldn't find information as to whether a file can be associated
with more than one module; if this is indeed the case, then this is cool
technology -- mainly because it works in a shipping product, compared to
UNIX filesystem stacking implementations. Otherwise, it would greatly
diminish the technical usefulness of this idea, and turn it into something
of a system call trapping look-alike.
> Also, not that if hash is less than filesize, there's non-null chance that
> the signature will bind files that arem't identical - which means, it's
> unusable for any serious data storage unless it compares files bit-bit
> every time.
That's a stupid assertion to make if you don't know what sort of
hash they're using. Do you?
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
