Re: bug in BSD tar?
- From: Colin Percival <cperciva@xxxxxxxxxxx>
- Date: Mon, 28 May 2007 20:18:59 -0700
Steven Hartland wrote:
----- Original Message ----- From: "Colin Percival" <cperciva@xxxxxxxxxxx>
tar -xvzf test.tar.gz
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
cantiquedeno\353l1_loop.wav
tar: Error exit delayed from previous errors
This looks like fairly typical symptoms of gnutar being broken. What
makes you think that the archive created by BSD tar was invalid?
As a filename should have no bearing on what extended headers
are set.
Why not? In this case, bsdtar is detecting that the file name contains
non-7-bit-ascii characters and is emitting a pax header for that reason;
and since it can't suppress the pax header entirely, it goes ahead and
emits the "not vital but potentially useful" headers for the device #,
inode #, number of links, and high precision timestamps.
I still see no evidence that bsdtar is doing anything wrong.
Colin Percival
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: bug in BSD tar?
- From: Steven Hartland
- Re: bug in BSD tar?
- References:
- bug in BSD tar?
- From: Steven Hartland
- Re: bug in BSD tar?
- From: Colin Percival
- Re: bug in BSD tar?
- From: Steven Hartland
- bug in BSD tar?
- Prev by Date: Re: Unable to install FreeBSD from external USB cdrom
- Next by Date: Re: updating xorg-libraries 7.2 to 7.2.1
- Previous by thread: Re: bug in BSD tar?
- Next by thread: Re: bug in BSD tar?
- Index(es):
Relevant Pages
|
|
