2025-02-24 03:22:05 +01:00
|
|
|
Description
|
|
|
|
|
2025-02-24 04:16:02 +01:00
|
|
|
Plzip is a massively parallel (multi-threaded) implementation of lzip, fully
|
|
|
|
compatible with lzip 1.4 or newer. Plzip uses the lzlib compression library.
|
|
|
|
|
|
|
|
Lzip is a lossless data compressor with a user interface similar to the
|
|
|
|
one of gzip or bzip2. Lzip can compress about as fast as gzip (lzip -0)
|
|
|
|
or compress most files more than bzip2 (lzip -9). Decompression speed is
|
|
|
|
intermediate between gzip and bzip2. Lzip is better than gzip and bzip2
|
|
|
|
from a data recovery perspective. Lzip has been designed, written and
|
|
|
|
tested with great care to replace gzip and bzip2 as the standard
|
|
|
|
general-purpose compressed format for unix-like systems.
|
2025-02-24 03:22:05 +01:00
|
|
|
|
2025-02-24 04:01:20 +01:00
|
|
|
Plzip can compress/decompress large files on multiprocessor machines
|
|
|
|
much faster than lzip, at the cost of a slightly reduced compression
|
2025-02-24 04:08:13 +01:00
|
|
|
ratio (0.4 to 2 percent larger compressed files). Note that the number
|
|
|
|
of usable threads is limited by file size; on files larger than a few GB
|
|
|
|
plzip can use hundreds of processors, but on files of only a few MB
|
|
|
|
plzip is no faster than lzip.
|
2025-02-24 04:04:37 +01:00
|
|
|
|
|
|
|
When compressing, plzip divides the input file into chunks and
|
|
|
|
compresses as many chunks simultaneously as worker threads are chosen,
|
2025-02-24 04:12:46 +01:00
|
|
|
creating a multimember compressed file.
|
2025-02-24 04:04:37 +01:00
|
|
|
|
|
|
|
When decompressing, plzip decompresses as many members simultaneously as
|
|
|
|
worker threads are chosen. Files that were compressed with lzip will not
|
2025-02-24 04:15:16 +01:00
|
|
|
be decompressed faster than using lzip (unless the '-b' option was used)
|
2025-02-24 04:04:37 +01:00
|
|
|
because lzip usually produces single-member files, which can't be
|
|
|
|
decompressed in parallel.
|
2025-02-24 03:22:05 +01:00
|
|
|
|
2025-02-24 04:16:02 +01:00
|
|
|
The lzip file format is designed for data sharing and long-term archiving,
|
|
|
|
taking into account both data integrity and decoder availability:
|
2025-02-24 04:04:02 +01:00
|
|
|
|
|
|
|
* The lzip format provides very safe integrity checking and some data
|
2025-02-24 04:16:02 +01:00
|
|
|
recovery means. The lziprecover program can repair bit flip errors
|
2025-02-24 04:04:02 +01:00
|
|
|
(one of the most common forms of data corruption) in lzip files,
|
|
|
|
and provides data recovery capabilities, including error-checked
|
|
|
|
merging of damaged copies of a file.
|
|
|
|
|
|
|
|
* The lzip format is as simple as possible (but not simpler). The
|
2025-02-24 04:16:02 +01:00
|
|
|
lzip manual provides the source code of a simple decompressor
|
|
|
|
along with a detailed explanation of how it works, so that with
|
|
|
|
the only help of the lzip manual it would be possible for a
|
|
|
|
digital archaeologist to extract the data from a lzip file long
|
|
|
|
after quantum computers eventually render LZMA obsolete.
|
2025-02-24 04:04:02 +01:00
|
|
|
|
2025-02-24 04:07:51 +01:00
|
|
|
* Additionally the lzip reference implementation is copylefted, which
|
|
|
|
guarantees that it will remain free forever.
|
2025-02-24 04:01:20 +01:00
|
|
|
|
2025-02-24 04:04:37 +01:00
|
|
|
A nice feature of the lzip format is that a corrupt byte is easier to
|
|
|
|
repair the nearer it is from the beginning of the file. Therefore, with
|
|
|
|
the help of lziprecover, losing an entire archive just because of a
|
|
|
|
corrupt byte near the beginning is a thing of the past.
|
|
|
|
|
2025-02-24 04:16:02 +01:00
|
|
|
Plzip uses the same well-defined exit status values used by lzip, which
|
|
|
|
makes it safer than compressors returning ambiguous warning values (like
|
|
|
|
gzip) when it is used as a back end for other programs like tar or zutils.
|
2025-02-24 04:02:39 +01:00
|
|
|
|
2025-02-24 04:16:02 +01:00
|
|
|
Plzip will automatically use for each file the largest dictionary size
|
|
|
|
that does not exceed neither the file size nor the limit given. Keep in
|
|
|
|
mind that the decompression memory requirement is affected at
|
|
|
|
compression time by the choice of dictionary size limit.
|
2025-02-24 04:04:02 +01:00
|
|
|
|
2025-02-24 04:02:39 +01:00
|
|
|
When compressing, plzip replaces every file given in the command line
|
|
|
|
with a compressed version of itself, with the name "original_name.lz".
|
|
|
|
When decompressing, plzip attempts to guess the name for the decompressed
|
|
|
|
file from that of the compressed file as follows:
|
|
|
|
|
|
|
|
filename.lz becomes filename
|
|
|
|
filename.tlz becomes filename.tar
|
|
|
|
anyothername becomes anyothername.out
|
|
|
|
|
|
|
|
(De)compressing a file is much like copying or moving it; therefore plzip
|
|
|
|
preserves the access and modification dates, permissions, and, when
|
2025-02-24 04:16:02 +01:00
|
|
|
possible, ownership of the file just as 'cp -p' does. (If the user ID or
|
2025-02-24 04:02:39 +01:00
|
|
|
the group ID can't be duplicated, the file permission bits S_ISUID and
|
|
|
|
S_ISGID are cleared).
|
|
|
|
|
|
|
|
Plzip is able to read from some types of non regular files if the
|
2025-02-24 04:16:02 +01:00
|
|
|
'--stdout' option is specified.
|
2025-02-24 03:22:05 +01:00
|
|
|
|
2025-02-24 03:54:35 +01:00
|
|
|
If no file names are specified, plzip compresses (or decompresses) from
|
|
|
|
standard input to standard output. In this case, plzip will decline to
|
|
|
|
write compressed output to a terminal, as this would be entirely
|
|
|
|
incomprehensible and therefore pointless.
|
|
|
|
|
2025-02-24 04:16:02 +01:00
|
|
|
Plzip will correctly decompress a file which is the concatenation of two or
|
|
|
|
more compressed files. The result is the concatenation of the corresponding
|
|
|
|
decompressed files. Integrity testing of concatenated compressed files is
|
|
|
|
also supported.
|
|
|
|
|
|
|
|
LANGUAGE NOTE: Uncompressed = not compressed = plain data; it may never
|
|
|
|
have been compressed. Decompressed is used to refer to data which have
|
|
|
|
undergone the process of decompression.
|
2025-02-24 03:54:35 +01:00
|
|
|
|
|
|
|
|
2025-02-24 04:16:02 +01:00
|
|
|
Copyright (C) 2009-2019 Antonio Diaz Diaz.
|
2025-02-24 03:22:05 +01:00
|
|
|
|
|
|
|
This file is free documentation: you have unlimited permission to copy,
|
|
|
|
distribute and modify it.
|
|
|
|
|
|
|
|
The file Makefile.in is a data file used by configure to produce the
|
2025-02-24 03:33:22 +01:00
|
|
|
Makefile. It has the same copyright owner and permissions that configure
|
|
|
|
itself.
|