[Cialug] Tar file corruption

Tue Apr 30 14:45:53 CDT 2013

On Apr 30, 2013, at 12:26 PM, David Bierce <david at bierce.org> wrote:

> I thought bzip2 just looked at a single block of data that was what ever the input blocksize is set to, then compressed it and moved on to the next chunk of data entirely seperate from the previous and next block.  Does it really have a container beyond input block size?

Bzip2 blocks are not interdependent, but that 900k you're talking about is the output block size. In theory it can represent up to ~50 MB of input data, assuming you had a really pattern-tastic input.

	Zach

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2746 bytes
Desc: not available
URL: <http://cialug.org/pipermail/cialug/attachments/20130430/06b079e0/attachment.bin>