Re:Why not tar? Limitations of the tar file format.
by fhars on Monday September 06, 2010 @01:47AM
(#1665997)
That is exactly why the lackof in-archive compression is bad, with tar you lose tje whole rest of the archive on a single bit error, with in-archive compression you lose just the file the error is located in.
Re:Why not tar? Limitations of the tar file format.
by btilly on Monday September 06, 2010 @02:19AM
(#1666052)
Also tar's behavior gives you better compression in the common (at least on Unix) case of many small text files with related content.
In other words the trade-off is exactly the opposite of what had been guessed above.
Re:Why not tar? Limitations of the tar file format.
by gaius on Monday September 06, 2010 @08:41AM
(#1666527)
tar never cared about encryption or compression because mostly you would get them "for free" in your tape library anyway.
Re:Why not tar? Limitations of the tar file format.
by dagw on Monday September 06, 2010 @02:58AM
(#1666122)
The pkzip format allows you to "zip" data uncompressed if you are worried about that. Then you can trivially unpack your files using nothing but seek and read for those cases where you also accidentally misplace your last copy of unzip.
Re:Why not tar? Limitations of the tar file format.
by acqq on Monday September 06, 2010 @03:56AM
(#1666196)
It also has file description before the copy of the file data and at the second copy at the end of the whole archive, allowing fast listing of the content or location inside of the archive, exactly as the article would want.
The only thing pkzip doesn't cover in the original format is unix/linux specific metadata, but maybe this was/can be added. I use info-zip when the metadata don't matter but tar when they do (but even tar has its limitations with working with unix/linux metadata).
Re:Why not tar? Limitations of the tar file format.
by dagw on Monday September 06, 2010 @04:25AM
(#1666242)
pkzip does reserve the posibility for an arbitrary length extra field connected to each file. According to the spec (http://www.pkware.com/documents/casestudies/APPNOTE.TXT) this is for "additional information...for special needs or for specific platforms". All compatible zip tools are required to ignore all information in this field that it doesn't understand so you can basically write whatever you want there (although the spec does offer a recommended format for writing to this field). So if you write a special ACL preserving zip implementation, you can still unpack the file with any other zip implementation that knows nothing of your special version.
Re:Why not tar? Limitations of the tar file format.
by bootload on Monday September 06, 2010 @03:30AM
(#1666158)
"... The pkzip format allows you to "zip" data uncompressed if you are worried about that. ..."
Didn't know that & must check the docs again.
Re:Why not tar? Limitations of the tar file format.
by nitrogen on Monday September 06, 2010 @06:39PM
(#1667556)
Some Zip applications show uncompressed files as being compressed with the "Store" algorithm instead of "Deflate".
Re:Why not tar? Limitations of the tar file format.
by masklinn on Monday September 06, 2010 @01:53AM
(#1666006)
> That can be an advantage. Space isn't always what I want for backups
Most if not all "compression" formats (and software) offer a "store" compressor which stores the data as-is, without applying any compression filter.
That can be an advantage. Space isn't always what I want for backups - I want the original data back and compression gone wrong (tar -zxvf) is just another way to loose data.