shouldn't tar quit at end of archive?
Rob Landley
rob at landley.net
Fri Apr 7 23:51:24 UTC 2006
On Thursday 06 April 2006 8:22 am, Paul Fox wrote:
> > > 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.
But you can't legitimately have two in a row from that cause. :)
> 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.
That is _definitely_ not the correct solution.
Rob
--
Never bet against the cheap plastic solution.
More information about the busybox
mailing list