shouldn't tar quit at end of archive?

[Paul Fox]

 > > From: Paul Fox [mailto:pgf at brightstareng.com]=20
 > <snip>
 > > second, it causes tar to exit when it detects the first occurence
 > > of a null header in the archive, rather than waiting for the
 > > second such header.  not all tar archives are terminated with two
 > > null headers.
 > 
 > Look at this: http://www.busybox.net/lists/busybox/2001-May/003341.html
 > Maybe this is the original reason why it tried to read everything
 > past the first empty block.

i don't think that's the whole story, but it's certainly worth keeping
in mind that the filename can legitimately be all-null.

i'm going to be out of town until the 17th, so won't be able to
look at this again, but i'd also be happy if someone else decided
they wanted to finish it off.  for the record -- i still think
the solution i proposed yesterday (only consume the input if it's
an internally spawned decompressor) is the correct one.

paul
=---------------------
 paul fox, pgf at brightstareng.com