From owner-freebsd-stable@FreeBSD.ORG Tue May 29 23:15:39 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 31C7916A468; Tue, 29 May 2007 23:15:39 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.freebsd.org (Postfix) with ESMTP id A243513C45A; Tue, 29 May 2007 23:15:38 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (y6opgh2ilkzo4pwy@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id l4TNFb9g087653; Tue, 29 May 2007 16:15:37 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id l4TNFbDq087652; Tue, 29 May 2007 16:15:37 -0700 (PDT) (envelope-from jmg) Date: Tue, 29 May 2007 16:15:36 -0700 From: John-Mark Gurney To: Steven Hartland Message-ID: <20070529231536.GA4602@funkthat.com> Mail-Followup-To: Steven Hartland , Colin Percival , freebsd-stable@freebsd.org References: <465B9BA3.30905@freebsd.org> <00fe01c7a1de$aff18080$b6db87d4@multiplay.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00fe01c7a1de$aff18080$b6db87d4@multiplay.co.uk> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-stable@freebsd.org, Colin Percival Subject: Re: bug in BSD tar? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 May 2007 23:15:39 -0000 Steven Hartland wrote this message on Tue, May 29, 2007 at 11:46 +0100: > ----- Original Message ----- > From: "Colin Percival" > >>----- Original Message ----- From: "Colin Percival" > >>>>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. > > I suppose this then comes down to the fact that gnu tar is the prevalent > version out there and as such with BSD creating archives which are > incompatible with that leads to problems. From our side we'll have to > switch to using gnutar until this issue is resolved as we need to ensure > compatibility. Is the file incorrect when extracted? or is this a mater of gtar throwing an error because of the tar format, and an option to bsdtar could be provided to change the output tar format? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."