doc: update README.txt

darcs-hash:7859cafe560f16fb21f0e01d3fa50bd8397a98a1

diff --git a/zfec/README.txt b/zfec/README.txt
index c91634698e46813dc7dd0c2c5e41a59b344c9674..6d9300714b7ed4a2af4b1fc5575391845221f1e7 100644 (file)
--- a/zfec/README.txt
+++ b/zfec/README.txt
@@ -103,21 +103,19 @@ input to the encoding step.
 
  * Command-Line Tool
 
-NOTE: the format of the sharefiles was changed in zfec v1.1 to allow K == 1 and
-K == M.  This change of the format of sharefiles means that zfec >= v1.1 cannot
-read sharefiles produced by zfec < v1.1.
-
 The bin/ directory contains two Unix-style, command-line tools "zfec" and
 "zunfec".  Execute "zfec --help" or "zunfec --help" for usage instructions.
 
 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" 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.
+well with zfec include "GNU tar" or "7z" a.k.a. "p7zip" for archiving multiple
+files and directories into one file, "rzip" 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.
+Note that if 7z is used for archiving then it also does very good compression,
+so you don't need a separate compressor in that case.
 
 
  * Performance Measurements