4 pixz \- parallel, indexing version of XZ
9 \fB/usr/bin/pixz\fR input output.pxz
14 \fB/usr/bin/pixz\fR -d input.pxz output
19 \fB/usr/bin/pixz\fR -l input.tpxz
24 \fB/usr/bin/pixz\fR -x /path/to/file < input.tpxz
30 The existing XZ Utils ( http://tukaani.org/xz/ ) provide great compression
31 in the .xz file format, but they have two significant problems:
38 They are single-threaded, while most users nowadays have multi-core computers.
44 The .xz files they produce are just one big block of compressed data, rather than a collection of smaller blocks. This makes random access to the original data impossible.
48 With pixz, both these problems are solved.
53 Specifying input and output:
58 $ pixz < foo.tar > foo.tpxz
63 Same as 'pixz foo.tar foo.tpxz'
70 $ pixz -i foo.tar -o foo.tpxz
75 Ditto. These both work for -x, -d and -l too, eg:
82 $ pixz -x -i foo.tpxz -o foo.tar file1 file2 ...
87 # Extract the files from foo.tpxz into foo.tar
99 Compress it to foo.tpxz, removing the original
111 Extract it to foo.tar, removing the original
117 Faster, worse compression.
120 Better, slower compression.
123 Cap the number of threads at <number>.
126 Compress but don't treat it as a tarball (don't index it).
129 Decompress, don't check that contents match index.
132 List the xz blocks instead of files.
135 Running pixz without the -t flag will cause it to treat the input
136 as a tarball, as long as it looks vaguely tarball-like. This means if the
137 file starts with at least 1024 zero bytes, pixz will assume it's empty, and
138 truncate the output! If your input files aren't tarballs, run with -t or
139 face possible data-loss.