From owner-freebsd-ports@FreeBSD.ORG  Tue Jul 20 04:30:34 2004
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 04B6516A4CE; Tue, 20 Jul 2004 04:30:34 +0000 (GMT)
Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net
	[66.166.149.50])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id AEE8543D31; Tue, 20 Jul 2004 04:30:32 +0000 (GMT)
	(envelope-from tim@kientzle.com)
Received: from kientzle.com (p54.kientzle.com [66.166.149.54])
	by kientzle.com (8.12.9/8.12.9) with ESMTP id i6K4UW90027100;
	Mon, 19 Jul 2004 21:30:32 -0700 (PDT)
	(envelope-from tim@kientzle.com)
Message-ID: <40FC9FC2.8050400@kientzle.com>
Date: Mon, 19 Jul 2004 21:29:54 -0700
From: Tim Kientzle <tim@kientzle.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Andrey Chernov <ache@nagual.pp.ru>
References: <40F963D8.6010201@freebsd.org>
	<20040719060730.GA87697@nagual.pp.ru>
In-Reply-To: <20040719060730.GA87697@nagual.pp.ru>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: ports@FreeBSD.ORG
cc: Tim Kientzle <kientzle@FreeBSD.ORG>
cc: current@FreeBSD.ORG
Subject: Re: NEW TAR
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2004 04:30:34 -0000

Andrey Chernov wrote:
> On Sat, Jul 17, 2004 at 10:37:28AM -0700, Tim Kientzle wrote:
>
>> * File format: bsdtar can read gtar files, including
>>   long file names, long link names, and sparse files.
>>   bsdtar can also read many other formats that gtar
>>   does not support.
>
> Addition:
> bsdtar can't write sparse archives (Yet?).

gtar has to be better at something!  ;-)

I have some ideas about sparse file handling,
but they're not gtar-compatible.  (The gtar
approach has a number of drawbacks.  The primary
one being that on many systems it requires reading
the entire file twice, once to find holes and again
to actually archive the file.  It is possible to
do both in one pass if you store the sparse file
data in a different fashion.)

Tim