From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 13:22:56 2004 Return-Path: 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 E881B16A4CE for ; Thu, 22 Jul 2004 13:22:56 +0000 (GMT) Received: from hetzner.co.za (lfw.hetzner.co.za [196.7.18.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D79543D41 for ; Thu, 22 Jul 2004 13:22:56 +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 1BndWu-000Bqw-00; Thu, 22 Jul 2004 15:22:36 +0200 To: SanD From: Ian FREISLICH In-Reply-To: Message from SanD <200407221325.i6MDPhqL024040@aaz.links.ru> Date: Thu, 22 Jul 2004 15:22:36 +0200 Sender: ianf@hetzner.co.za Message-Id: cc: current@freebsd.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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jul 2004 13:22:57 -0000 SanD wrote: > Ian wrote: > > How does dump handle sparse files? > Dump handles fine sparse files. Maybe I should have asked how does dump figure out that the files are sparse and if it's any more intelligent than a 2 pass read (I have no idea why 2 passes are required) or just blindly turning successive zeros into a seek offset, is there anything preventing BSD tar from doing the same? Ian -- Ian Freislich