summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorDaniel Baumann <mail@daniel-baumann.ch>2015-11-07 05:00:44 +0000
committerDaniel Baumann <mail@daniel-baumann.ch>2015-11-07 05:00:44 +0000
commit9abf3b0a7bda1563cc5eb6537459e9486b622af7 (patch)
tree99db223dbca09d5dac8e06a1f46a4c541fb5e9ba /README
parentAdding debian version 1.2-4. (diff)
downloadlunzip-9abf3b0a7bda1563cc5eb6537459e9486b622af7.tar.xz
lunzip-9abf3b0a7bda1563cc5eb6537459e9486b622af7.zip
Merging upstream version 1.3~rc1.
Signed-off-by: Daniel Baumann <mail@daniel-baumann.ch>
Diffstat (limited to 'README')
-rw-r--r--README12
1 files changed, 12 insertions, 0 deletions
diff --git a/README b/README
index 217fb0a..f02c51b 100644
--- a/README
+++ b/README
@@ -5,6 +5,18 @@ small size makes it well suited for embedded devices or software
installers that need to decompress files but do not need compression
capabilities.
+Lunzip uses the same well-defined exit status values used by bzip2,
+which makes it safer when used in pipes or scripts than compressors
+returning ambiguous warning values, like gzip.
+
+The 4 factor integrity checking of the lzip format guarantees that the
+decompressed version of the data is identical to the original. This
+guards against corruption of the compressed data, and against undetected
+bugs in lunzip (hopefully very unlikely). The chances of data corruption
+going undetected are microscopic. Be aware, though, that the check
+occurs upon decompression, so it can only tell you that something is
+wrong. It can't help you recover the original uncompressed data.
+
If you ever need to recover data from a damaged lzip file, try the
lziprecover program.