Quote:
Originally Posted by geekmaster
But does your script need to decompress the files to SHA-1 them? If so, I hope on ramdisk, so as not to wear out my SSDs (all I have in this machine).
Really, "wear out" is not all that accurate -- the problem is with mostly-full SSDs, TRIM support has little free space to work in, so I need to periodically backup the drive, secure erase it, and restore it, to get my "factory fresh" write speed back (a bit cumbersome for an mSATA boot drive). SSDs get damn slow (like 10-percent speed) after written to a lot -- secure erase fixes that.
I still have (expensive) SSDs from back in the days before TRIM even existed. But still, even TRIM drives are rather ineffective unless you keep them mostly empty (yeah, like that ever happens, eh?)...
|
http://hg.minimodding.com/repos/cats/shacat.hg/
It doesn't (now) do xz compression, it does not recognize Amazon update_*.bin as a 'container' format.
It isn't very user friendly, but I am willing to help with examples as required.
oh -
and 20Gbytes of compressed archives is well within its limits.
Rethink -
There are already posted here some worked examples -
Also, a script that builds (@file level) concordances of the contents of the data file.