svn commit: trunk/busybox: scripts

Natanael Copa natanael.copa at gmail.com
Wed May 17 14:15:12 UTC 2006


On Tue, 2006-05-16 at 11:53 -0400, Rob Landley wrote:
> On Tuesday 16 May 2006 10:38 am, Natanael Copa wrote:
> > On Mon, 2006-05-15 at 13:17 -0400, Rob Landley wrote:
> > > On Saturday 13 May 2006 3:20 pm, Bernhard Fischer wrote:
> > >
> > > My testing on the tar coalesce writes patch found what might be a
> > > preexisting bug in busybox tar, that I need to track down and fix before
> > > I can apply that.
> >
> > Can I help you to track down this preexisting bug in tar?
> 
> I don't know yet if it is a preexisting bug.  It's in an area of code I didn't
> touch, but that could just mean I'm passing something stupid to other code.
> Haven't had time to look at it for a couple days, but it's on the todo list
> for later today...
> 
> Tarring up and extracting the linux-2.6.16 kernel tarball triggers it about
> halfway through the extract of the resulting tarball.  Easy enough to
> reproduce, but rather a long path to get to it through the code...

Checked out the trunk and busybox tar gives me an error message:

tar: pax is not tar

However, today have been busy so I havent been able to track it down.
It looks like the linux tar archive is a pax archive
(tar.formated.typeflag is obviously set to 'g'). I guess gnu tar handles
pax format as well, while busybox tar does not. (looks like bsd tar
handles it too)

Could be something else you are seeing. Here it does not even go
halfway.

--
Natanael Copa




More information about the busybox mailing list