From owner-freebsd-current@FreeBSD.ORG  Thu Jul 22 12:37:42 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 667A816A4CF
	for <current@freebsd.org>; Thu, 22 Jul 2004 12:37:42 +0000 (GMT)
Received: from hetzner.co.za (lfw.hetzner.co.za [196.7.18.226])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 98FA843D3F
	for <current@freebsd.org>; Thu, 22 Jul 2004 12:37:41 +0000 (GMT)
	(envelope-from ianf@hetzner.co.za)
Received: from localhost ([127.0.0.1])
	by hetzner.co.za with esmtp (Exim 3.36 #1)
	id 1Bncom-000BdL-00; Thu, 22 Jul 2004 14:37:00 +0200
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
From: Ian FREISLICH <if@hetzner.co.za>
In-Reply-To: Message from Garrett Wollman <wollman@khavrinen.lcs.mit.edu> 
	<200407211622.i6LGMZrm040478@khavrinen.lcs.mit.edu> 
Date: Thu, 22 Jul 2004 14:37:00 +0200
Sender: ianf@hetzner.co.za
Message-Id: <E1Bncom-000BdL-00@hetzner.co.za>
cc: current@FreeBSD.ORG
cc: Daniel Lang <dl@leo.org>
Subject: Re: NEW TAR 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jul 2004 12:37:42 -0000

Garrett Wollman wrote:
> <<On Wed, 21 Jul 2004 17:14:27 +0200, Daniel Lang <dl@leo.org> said:
> 
> > I do not see, why it is important if the original file was sparse
> > at all or maybe in different places.
> 
> You've never run out of disk space as a result of a sparse file
> becoming non-sparse?

So, are you arguing for or against tar converting files into sparse
files where it can as Daniel proposes?

I have heard stories about D.O.S. attacking backups by creating a
large sparse file that would be backed up using tar.  Daniel's
proposal would be a boon in this instance.

How does dump handle sparse files?

Ian

--
Ian Freislich