On Tue, Sep 22, 2009 at 11:55:54PM -0400, Peter Renzland wrote:
On 09 Sep 20, at 19:31 , Denys Vlasenko wrote:
On Sunday 20 September 2009 23:51, Peter Renzland wrote:
It appears ironic that Snow Leopard, The World's most advanced OS,
has switched to the POSIX tar format, which according to
On Wed, Sep 23, 2009 at 5:55 AM, Peter Renzland pe...@dancing.org wrote:
On 09 Sep 20, at 19:31 , Denys Vlasenko wrote:
On Sunday 20 September 2009 23:51, Peter Renzland wrote:
It appears ironic that Snow Leopard, The World's most advanced OS,
has switched to the POSIX tar format, which
On 09 Sep 23, at 07:11 , Denys Vlasenko wrote:
On Wed, Sep 23, 2009 at 5:55 AM, Peter Renzland pe...@dancing.org
wrote:
On 09 Sep 20, at 19:31 , Denys Vlasenko wrote:
On Sunday 20 September 2009 23:51, Peter Renzland wrote:
It appears ironic that Snow Leopard, The World's most advanced
Since there is no longer a current POSIX tar standard, perhaps it might
make
sense to create a Busybox term:
NEW APPLE COMPATIBILITY which is equivalent to OLDGNU COMPATIBILITY.
I think the question is: do we need to have
FEATURE_TAR_OLDGNU_COMPATIBILITY
at all? Maybe it makes sense to
On 09 Sep 23, at 11:20 , Denys Vlasenko wrote:
Since there is no longer a current POSIX tar standard, perhaps it
might
make
sense to create a Busybox term:
NEW APPLE COMPATIBILITY which is equivalent to OLDGNU
COMPATIBILITY.
I think the question is: do we need to have
On 09 Sep 23, at 11:20 , Denys Vlasenko wrote:
Since there is no longer a current POSIX tar standard, perhaps it
might
make
sense to create a Busybox term:
NEW APPLE COMPATIBILITY which is equivalent to OLDGNU
COMPATIBILITY.
I think the question is: do we need to have
On 09 Sep 20, at 19:31 , Denys Vlasenko wrote:
On Sunday 20 September 2009 23:51, Peter Renzland wrote:
It appears ironic that Snow Leopard, The World's most advanced OS,
has switched to the POSIX tar format, which according to BusyBox
terminology requires OLDGNU_COMPATIBILITY.
I do not think
accept e.g. -123 too :)
*/
str[len] = '\0';
v = strtoull(str, str, 8);
if (*str (!ENABLE_FEATURE_TAR_OLDGNU_COMPATIBILITY || *str !=
' '))
bb_error_msg_and_die(corrupted octal value in tar header);
return v;
}
#define GET_OCTAL(a) getOctal((a), sizeof(a))
Can
switched to the POSIX tar format, which according to BusyBox
terminology requires OLDGNU_COMPATIBILITY.
# ./busybox tar tf /tmp/snow.tar
tar: corrupted octal value in tar header
Can someone please explain what is meant by corrupted octal value,
in this context?
What is this message trying
Attempts to extract tar files produced by Mac OS X 10.6 (Snow Leopard)
files fail with the error:
tar: corrupted octal value in tar header from
BusyBox v1.14.2 (2009-07-02 18:01:37 CEST) built-in shell (ash)
On GNU/Linux 2.4.20, on a Linksys WRT54GL Router (MIPS) running Tomato
1.25
On Saturday 19 September 2009 15:09, Peter Renzland wrote:
Attempts to extract tar files produced by Mac OS X 10.6 (Snow Leopard)
files fail with the error:
tar: corrupted octal value in tar header from
BusyBox v1.14.2 (2009-07-02 18:01:37 CEST) built-in shell (ash)
On GNU/Linux 2.4.20
11 matches
Mail list logo
