Linux / Unix Command: bunzip2--reference

http://linux.about.com/library/cmd/blcmdl1_bunzip2.htm

NAME

bzip2,bunzip2 - a block-sorting file compressor,v1.0.2?bzcat - decompresses files to stdout?bzip2recover - recovers data from damaged bzip2 files

?

SYNOPSIS

bzip2?[?-cdfkqstvzVL123456789?] [?filenames ...?]?bunzip2?[?-fkvsVL?] [?filenames ...?]?bzcat?[?-s?] [?filenames ...?]?bzip2recover?filename

?

DESCRIPTION

bzip2?compresses files using the Burrows-Wheeler block sorting text compression algorithm,and Huffman coding. Compression is generally considerably better than that achieved by more conventional LZ77/LZ78-based compressors,and approaches the performance of the PPM family of statistical compressors.

The command-line options are deliberately very similar to those of?GNU gzip,?but they are not identical.

bzip2?expects a list of file names to accompany the command-line flags. Each file is replaced by a compressed version of itself,with the name "original_name.bz2". Each compressed file has the same modification date,permissions,and,when possible,ownership as the corresponding original,so that these properties can be correctly restored at decompression time. File name handling is naive in the sense that there is no mechanism for preserving original file names,ownerships or dates in filesystems which lack these concepts,or have serious file name length restrictions,such as MS-DOS.

bzip2?and?bunzip2?will by default not overwrite existing files. If you want this to happen,specify the -f flag.

If no file names are specified,?bzip2?compresses from standard input to standard output. In this case,?bzip2?will decline to write compressed output to a terminal,as this would be entirely incomprehensible and therefore pointless.

bunzip2?(or?bzip2 -d)?decompresses all specified files. Files which were not created by?bzip2?will be detected and ignored,and a warning issued.?bzip2?attempts 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,?.tbz2?or?.tbz,?bzip2complains that it cannot guess the name of the original file,and uses the original name with.out?appended.

As with compression,supplying no filenames causes decompression from standard input to standard output.

bunzip2?will correctly decompress a file which is the concatenation of two or more compressed files. The result is the concatenation of the corresponding uncompressed files. Integrity testing (-t) of concatenated compressed files is also supported.

You can also compress or decompress files to the standard output by giving the -c flag. Multiple files may be compressed and decompressed like this. The resulting outputs are fed sequentially to stdout. Compression of multiple files in this manner generates a stream containing multiple compressed file representations. Such a stream can be decompressed correctly only by?bzip2?version 0.9.0 or later. Earlier versions of?bzip2?will stop after decompressing the first file in the stream.

bzcat?(or?bzip2 -dc)?decompresses all specified files to the standard output.

bzip2?will read arguments from the environment variables?BZIP2?and?BZIP,?in that order,and will process them before 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 slightly larger than the original. Files of less than about one hundred bytes tend to get larger,since the compression mechanism has a constant overhead in the region of 50 bytes. Random data (including the output of most file compressors) is coded at about 8.05 bits per byte,giving an expansion of around 0.5%.

As a self-check for your protection,?bzip2?uses 32-bit CRCs to make sure that the decompressed version of a file is identical to the original. This guards against corruption of the compressed data,and against undetected bugs in?bzip2?(hopefully very unlikely). The chances of data corruption going undetected is microscopic,about one chance in four billion for each file processed. 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. You can use?bzip2recover?to try to recover data from damaged files.

Return values: 0 for a normal exit,1 for environmental problems (file not found,invalid flags,I/O errors,&c),2 to indicate a corrupt compressed file,3 for an internal consistency error (eg,bug) which caused?bzip2?to panic.

（编辑：济南站长网）

【声明】本站内容均来自网络，其相关言论仅代表作者个人观点，不代表本站立场。若无意侵犯到您的权利，请及时与联系站长删除相关内容!