The command-line options are deliberately very similar to those of GNU gzip, but they are not identical.
bzip2expects a list of file names to accompany thecommand-line flags. Each file is replaced by a compressed version ofitself, with the name "original_name.bz2". Each compressed filehas the same modification date, permissions, and, when possible,ownership as the corresponding original, so that these properties canbe correctly restored at decompression time. File name handling isnaive in the sense that there is no mechanism for preserving originalfile names, permissions, ownerships or dates in filesystems which lackthese concepts, or have serious file name length restrictions, such asMS-DOS.
bzip2andbunzip2will by default not overwrite existingfiles. If you want this to happen, specify the -f flag.
If no file names are specified,bzip2compresses from standardinput to standard output. In this case,bzip2will decline towrite compressed output to a terminal, as this would be entirelyincomprehensible and therefore pointless.
bunzip2(orbzip2 -d) decompresses allspecified files. Files which were not created by bzip2will be detected and ignored, and a warning issued. bzip2attempts to guess the filename for the decompressed file from that of the compressed file as follows:
filename.bz2 becomes filename
filename.bz becomes filename
filename.tbz2 becomes filename.tar
filename.tbz becomes filename.tar
anyothername becomes anyothername.out
If the file does not end in one of the recognised endings, .bz2, .bz, .tbz2or.tbz, bzip2 complains that it cannotguess the name of the original file, and uses the original namewith.outappended.
As with compression, supplying nofilenames causes decompression from standard input to standard output.
bunzip2 will correctly decompress a file which is theconcatenation of two or more compressed files. The result is theconcatenation of the corresponding uncompressed files. Integritytesting (-t) of concatenated compressed files is also supported.
You can also compress or decompress files to the standard output bygiving the -c flag. Multiple files may be compressed anddecompressed like this. The resulting outputs are fed sequentially tostdout. Compression of multiple files in this manner generates a streamcontaining multiple compressed file representations. Such a streamcan be decompressed correctly only bybzip2 version 0.9.0 orlater. Earlier versions ofbzip2will stop after decompressingthe first file in the stream.
bzcat(orbzip2 -dc) decompresses all specified files tothe standard output.
bzip2will read arguments from the environment variablesBZIP2andBZIP,in that order, and will process thembefore any arguments read from the command line. This gives a convenient way to supply default arguments.
Compression is always performed, even if the compressed file is slightlylarger than the original. Files of less than about one hundred bytestend to get larger, since the compression mechanism has a constantoverhead in the region of 50 bytes. Random data (including the outputof most file compressors) is coded at about 8.05 bits per byte, givingan expansion of around 0.5%.
As a self-check for your protection, bzip2uses 32-bit CRCs tomake sure that the decompressed version of a file is identical to theoriginal. This guards against corruption of the compressed data, andagainst undetected bugs inbzip2(hopefully very unlikely). Thechances of data corruption going undetected is microscopic, about onechance in four billion for each file processed. Be aware, though, thatthe check occurs upon decompression, so it can only tell you thatsomething is wrong. It can't help you recover the original uncompresseddata. You can use bzip2recoverto try to recover data fromdamaged files.
Return values: 0 for a normal exit, 1 for environmental problems (filenot found, invalid flags, I/O errors, &c), 2 to indicate a corruptcompressed file, 3 for an internal consistency error (eg, bug) whichcausedbzip2to panic.
bzip2 normally declines to decompress files which don't have thecorrect magic header bytes. If forced (-f), however, it will passsuch files through unmodified. This is how GNU gzip behaves.
During compression, -s selects a block size of 200k, which limitsmemory use to around the same figure, at the expense of your compressionratio. In short, if your machine is low on memory (8 megabytes orless), use -s for everything. See MEMORY MANAGEMENT below.
Important: Use the man command (% man) to see how a command is used on your particular computer.
>> Linux/Unix Command Library
>> Shell Command Library