5.3-RC2 tar breaks operation with "(null)"
Kris Kennaway
kris at obsecurity.org
Wed Nov 17 07:46:58 PST 2004
On Wed, Nov 17, 2004 at 04:51:01PM +0000, Andrew Sinclair wrote:
> <>I checked the changelog for that. There is a minor change to its
> handling of failed writes to the archive, which is quite the opposite of
> what I am trying to do. My disc is unsuprisingly screwed and the
> drive/filesystem returns zero filled blocks where it fails to read. I
> managed to work around it with dd and gtar:
>
> dd if=/dvdrom/20041116.tgz of=/home/shared/mec/20041116.tgz
> gtar --ignore-zero --ignore-failed-read -xvf
> /home/shared/mec/20041116.tgz
>
> So a PPT and a PNG were garbled. No big deal. Since bsdtar is now the
> default Tape ARchiver, shouldn't it include the options of its
> predecessor? I would assert --ignore-zero on plain files and allow
> --ignore-failed-read at least.
You can (and should) discuss this with the author, but bsdtar isn't
currently intended to be a 100% replacement for gtar, particularly for
the more obscure options. If you need gtar, you can always use it
instead.
Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20041117/2ee279b0/attachment.bin
More information about the freebsd-questions
mailing list