From owner-freebsd-stable@FreeBSD.ORG Tue May 29 10:49:02 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 934FD16A55A; Tue, 29 May 2007 10:49:02 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id C87F113C465; Tue, 29 May 2007 10:49:01 +0000 (UTC) (envelope-from killing@multiplay.co.uk) X-Spam-Checker-Version: SpamAssassin 3.1.5 (2006-08-29) on core6.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, USER_IN_WHITELIST, USER_IN_WHITELIST_TO autolearn=ham version=3.1.5 Received: from r2d2 ([212.135.219.182]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon PRO v9.5.4) with ESMTP id md50003865618.msg; Tue, 29 May 2007 11:47:21 +0100 Message-ID: <00fe01c7a1de$aff18080$b6db87d4@multiplay.co.uk> From: "Steven Hartland" To: "Colin Percival" References: <005d01c7a169$b48c7390$b6db87d4@multiplay.co.uk><465B4C2B.6060104@freebsd.org><003701c7a187$bc8f8e10$b6db87d4@multiplay.co.uk> <465B9BA3.30905@freebsd.org> Date: Tue, 29 May 2007 11:46:58 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-MDRemoteIP: 212.135.219.182 X-Return-Path: killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-Spam-Processed: multiplay.co.uk, Tue, 29 May 2007 11:47:22 +0100 X-MDAV-Processed: multiplay.co.uk, Tue, 29 May 2007 11:47:22 +0100 Cc: freebsd-stable@freebsd.org Subject: Re: bug in BSD tar? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list 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 10:49:02 -0000 ----- 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. Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk.