Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 May 2002 14:21:21 +0200
From:      Laurent LEVIER <llevier@argosnet.com>
To:        Paul Eggert <eggert@twinsun.com>
Cc:        freebsd-bugs@FreeBSD.ORG
Subject:   Re: GNU tar port on FreeBSD bug...
Message-ID:  <5.1.0.14.2.20020510141612.01fec170@belegost.cimternet.com>
In-Reply-To: <200205091850.g49IoWe03311@shade.twinsun.com>
References:  <5.1.0.14.2.20020509163545.01f41690@belegost.cimternet.com> <5.1.0.14.2.20020509163545.01f41690@belegost.cimternet.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Paul,

The fact is I dont have a version number on the program itself as arguments 
and --help does not help. This is why I added FreeBSD infos...

"stringing" it, the only thing I found to help is: "GNU tar version 1.11.2"

Brgrds

At 20:50 09/05/2002, Paul Eggert wrote:
> > Date: Thu, 09 May 2002 16:41:29 +0200
> > From: Laurent LEVIER <llevier@argosnet.com>
> >
> > I found this little bug on GNU tar port on FreeBSD 4.5-sp2 (world)
> >
> > tar tvf answers:
> > -rw-r--r-- laurent/smbusers 1317064704 Apr  1 12:39 2002 OsgiliathC.mtf
> > -rw-r--r-- laurent/smbusers -1448130560 Apr  1 18:57 2002 OsgiliathD.mtf
>
>You don't mention which version of GNU tar you're using, but many of
>the bugs in that area have been fixed in the latest test version, which
>you can find in:
>
>ftp://alpha.gnu.org/gnu/tar/tar-1.13.25.tar.gz
>
> > Seems it is just a bad variable type problem to solve...
>
>It's a bit trickier than that, I'm afraid, as tar has to decode buggy
>size fields.  It's a 36-bit size field in the POSIX tar format, but
>many 32-bit tar implementations create incorrect size fields for files
>with 2**31 bytes or more.

Laurent LEVIER
IT Systems & Networks Security Expert




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.1.0.14.2.20020510141612.01fec170>