From: Zooko O'Whielacronx Date: Mon, 30 Apr 2007 18:08:19 +0000 (-0700) Subject: zfec: add mention of lrzip and edit text X-Git-Tag: allmydata-tahoe-0.2.0~53 X-Git-Url: https://git.rkrishnan.org/components/com_hotproperty/%22doc.html/architecture.txt?a=commitdiff_plain;h=74e01aa84979105ab9a500a39291ba3c640021a6;p=tahoe-lafs%2Ftahoe-lafs.git zfec: add mention of lrzip and edit text --- diff --git a/src/zfec/README.txt b/src/zfec/README.txt index 987cd3d7..a5e7648b 100644 --- a/src/zfec/README.txt +++ b/src/zfec/README.txt @@ -91,12 +91,13 @@ The bin/ directory contains two Unix-style, command-line tools "zfec" and Note: a Unix-style tool like "zfec" does only one thing -- in this case erasure coding -- and leaves other tasks to other tools. Other Unix-style -tools that go well with zfec include "GNU tar" for archiving multiple files and -directories into one file, "rzip" for compression, "GNU Privacy Guard" for -encryption, and "sha256sum" for integrity. It is important to do things in -order: first archive, then compress, then either encrypt or sha256sum, then -erasure code. Note that if GNU Privacy Guard is used for privacy, then it will -also ensure integrity, so the use of sha256sum is unnecessary in that case. +tools that go well with zfec include "GNU tar" for archiving multiple files +and directories into one file, "rzip" or "lrzip" for compression, and "GNU +Privacy Guard" for encryption or "sha256sum" for integrity. It is important +to do things in order: first archive, then compress, then either encrypt or +sha256sum, then erasure code. Note that if GNU Privacy Guard is used for +privacy, then it will also ensure integrity, so the use of sha256sum is +unnecessary in that case. * Performance Measurements