• 管理员
    了解作者
  • C/C++
    开发工具
  • 444KB
    文件大小
  • gz
    文件格式
  • 0
    收藏次数
  • 10 积分
    下载积分
  • 2528
    下载次数
  • 2001-01-10 05:39
    上传日期
高效率的一种通用压缩/解压程序
bzip.tar.gz
  • bzip2-0.9.0c
  • sample1.ref
    96.4KB
  • CHANGES
    1.3KB
  • bzlib_private.h
    13.5KB
  • manual_toc.html
    3.5KB
  • bzlib.h
    7.1KB
  • crctable.c
    6.3KB
  • bzip2.1
    14.1KB
  • Makefile
    1.1KB
  • bzlib.c
    42.3KB
  • manual_1.html
    3.8KB
  • sample1.bz2
    31.6KB
  • howbig.c
    737B
  • sample2.ref
    207.4KB
  • manual_4.html
    16.3KB
  • dlltest.dsp
    3.4KB
  • sample2.bz2
    72KB
  • LICENSE
    1.7KB
  • words3
    778B
  • manual.ps
    457.2KB
  • bzip2recover.c
    12.1KB
  • randtable.c
    5.3KB
  • manual_3.html
    53.5KB
  • libbz2.dsp
    4.2KB
  • decompress.c
    19.8KB
  • libbz2.def
    394B
  • words2
    185B
  • manual_2.html
    17.3KB
  • bzip2.txt
    16.5KB
  • bzip2.1.preformatted
    18.7KB
  • compress.c
    16.4KB
  • blocksort.c
    20.3KB
  • manual.texi
    82.5KB
  • huffman.c
    7.4KB
  • README
    4.6KB
  • bzip2.c
    44.6KB
  • words1
    103B
  • dlltest.c
    3KB
内容介绍
bzip2(1) bzip2(1) NAME bzip2, bunzip2 - a block-sorting file compressor, v0.9.0 bzcat - decompresses files to stdout bzip2recover - recovers data from damaged bzip2 files SYNOPSIS bzip2 [ -cdfkstvzVL123456789 ] [ 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 sta- tistical 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 com- mand-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 and permissions 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, per- missions and dates in filesystems which lack these con- cepts, 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 and restores all spec- ified files whose names end in ".bz2". Files without this suffix are ignored. Again, supplying no filenames causes decompression from standard input to standard output. bunzip2 will correctly decompress a file which is the con- catenation 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 com- pressed and decompressed like this. The resulting outputs are fed sequentially to stdout. Compression of multiple files in this manner generates a stream containing multi- ple 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 decom- pressing the first file in the stream. bzcat (or bzip2 -dc ) decompresses all specified files to the standard output. 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 corrup- tion 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 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. MEMORY MANAGEMENT Bzip2 compresses large files in blocks. The block size affects both the compression ratio achieved, and the amount of memory needed both for compression and decom- pression. The flags -1 through -9 specify the block size to be 100,000 bytes through 900,000 bytes (the default) respectively. At decompression-time, the block size used for compression is read from the header of the compressed file, and bunzip2 then allocates itself just enough memory to decompress the file. Since block sizes are stored in compressed files, it follows that the flags -1 to -9 are irrelevant to and so ignored during decompression. Compression and decompression requirements, in bytes, can be estimated as: Compression: 400k + ( 7 x block size ) Decompression: 100k + ( 4 x block size ), or 100k + ( 2.5 x block size ) Larger block sizes give rapidly diminishing marginal returns; most of the compression comes from the first two or three hundred k of block size, a fact worth bearing in mind when using bzip2 on small machines. It is also important to appreciate that the decompression memory requirement is set at compression-time by the choice of block size. For files compressed with the default 900k block size, bunzip2 will require about 3700 kbytes to decompress. To support decompression of any file on a 4 megabyte machine, bunzip2 has an option to decompress using approximately half this amount of memory, about 2300 kbytes. Decompres- sion speed is also halved, so you should use this option only where necessary. The relevant flag is -s. In general, try and use the largest block size memory con- straints allow, since that maximises the compression achieved. Compression and decompression speed are virtu- ally unaffected by block size. Another significant point applies to files which fit in a single block -- that means most files you'd encounter using a large block size. The amount of real memory touched is proportional to the size of the file, since the file is smaller than a block. For example, compressing a file 20,000 bytes long with the flag -9 will cause the compressor to allocate around 6700k of memory, but only touch 400k + 20000 * 7 = 540 kbytes of it. Similarly, the decompressor will allocate 3700k but only touch 100k + 20000 * 4 = 180 kbytes. Here is a table which summarises the maximum memory usage for different block sizes. Also recorded is the total compressed size for 14 files of the Calgary Text Compres- sion Corpus totalling 3,141,622 bytes. This column gives some feel for how compression varies with block size. These figures tend to understate the advantage of larger block sizes for larger files, since the Corpus is domi- nated by smaller files. Compress Decompress Decompress Corpus Flag usage
评论
    相关推荐
    • squashfs4.3.tar.gz
      squashfs4.3.tar.gz用于解压压缩squashfs格式的文件系统
    • Java压缩压缩tar.gz
      使用Java对文件夹压缩tar.gz文件,使用Java对tar.gz压缩文件解压
    • leveldb-1.15.0.tar.gz
      数据支持被Snappy函式库压缩[4],以减少Disk I/O提升效能 https://code.google.com/p/leveldb下载址. google被和谐了.无法正常,提供可以使用地址 解压之后进入目录:leveldb-1.15.0 执行:make,生成了: ...
    • hadoop-2.7.2.tar.gz
      根据apache源码编译的hadoop包,带snappy压缩解压即可使用
    • hadoop-2.7.2.tar.gz.zip
      为方便网络不畅通的同学下载,故上传至此无需积分,由于资源冲突于是又重新压缩解压后就是hadoop-2.7.2.tar.gz。Hadoop是一个由Apache基金会所开发的分布式系统基础架构。用户可以在不了解分布式底层细节的情况下...
    • compression-utils:简单易用的库来压缩解压 .tar.gz 格式的文件
      简单易用的库来压缩解压 .tar.gz 格式的文件。 该库是 Apache Commons Compress 库的简单包装器,但它提供了一个更易于使用的面向文件的界面。 安装 无论出于何种目的,您都可以按照您认为合适的方式使用该库。 我...
    • webtrack.tar.gz
      支持GB2312、GBK、UTF-8编码,能够对GZIP压缩的页面进行解压扫描;多路多核支持,可充分利用X86强大的计算能力进行高速数据扫描;稳定性高,引擎核心程序工作在应用层,不会影响到LINUX系统内核;基于网络的旁路部署...
    • lzo-2.04.tar.gz
      LZO 是致力于解压速度的一种数据压缩算法,LZO 是 Lempel-Ziv-Oberhumer 的缩写。这个算法是无损算法,参考实现程序是线程安全的。
    • ant操作7zip压缩解压 tar.gz
      7zip压缩解压 tar.gz,build.xml在压缩包里面。。。。。。。。。。。。。。
    • jdk-8u181-linux-i586.tar.gz 64位
      tar -xzvf file.tar.gz //解压tar.gz tar -xjvf file.tar.bz2 //解压 tar.bz2 tar –xZvf file.tar.Z //解压tar.Z unrar e file.rar //解压rar unzip file.zip //解压zip 总结 1、*.tar 用 tar –xvf 解压 2、*.gz ...