From owner-freebsd-ports@FreeBSD.ORG Tue Jul 20 07:03:33 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F20C916A4CE for ; Tue, 20 Jul 2004 07:03:33 +0000 (GMT) Received: from n33.kp.t-systems-sfr.com (n33.kp.t-systems-sfr.com [129.247.16.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3ECEA43D62 for ; Tue, 20 Jul 2004 07:03:33 +0000 (GMT) (envelope-from harti@freebsd.org) Received: from n81.sp.op.dlr.de (n81g.sp.op.dlr.de [129.247.163.1]) i6K73Fj38936; Tue, 20 Jul 2004 09:03:15 +0200 Received: from zeus.nt.op.dlr.de (zeus.nt.op.dlr.de [129.247.173.3]) i6K73Ff780086; Tue, 20 Jul 2004 09:03:15 +0200 Received: from beagle.kn.op.dlr.de (opkndnwsbsd178 [129.247.173.178]) by zeus.nt.op.dlr.de (8.11.7+Sun/8.9.1) with ESMTP id i6K73DV22301; Tue, 20 Jul 2004 09:03:13 +0200 (MET DST) Date: Tue, 20 Jul 2004 09:03:13 +0200 (CEST) From: Harti Brandt X-X-Sender: brandt@beagle.kn.op.dlr.de To: Tim Kientzle In-Reply-To: <40FC9FC2.8050400@kientzle.com> Message-ID: <20040720090203.N576@beagle.kn.op.dlr.de> References: <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> <40FC9FC2.8050400@kientzle.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: ports@freebsd.org cc: Andrey Chernov Subject: Re: NEW TAR X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Harti Brandt List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2004 07:03:34 -0000 On Mon, 19 Jul 2004, Tim Kientzle wrote: TK>Andrey Chernov wrote: TK>> On Sat, Jul 17, 2004 at 10:37:28AM -0700, Tim Kientzle wrote: TK>> TK>> > * File format: bsdtar can read gtar files, including TK>> > long file names, long link names, and sparse files. TK>> > bsdtar can also read many other formats that gtar TK>> > does not support. TK>> TK>> Addition: TK>> bsdtar can't write sparse archives (Yet?). TK> TK>gtar has to be better at something! ;-) TK> TK>I have some ideas about sparse file handling, TK>but they're not gtar-compatible. (The gtar TK>approach has a number of drawbacks. The primary TK>one being that on many systems it requires reading TK>the entire file twice, once to find holes and again TK>to actually archive the file. It is possible to TK>do both in one pass if you store the sparse file TK>data in a different fashion.) You may also talk with Joerg Schilling who's star supports sparse files. harti