From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 2 15:45:34 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EBC016A4E8 for ; Wed, 2 Aug 2006 15:45:34 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2152E43D76 for ; Wed, 2 Aug 2006 15:45:25 +0000 (GMT) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.221] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id k72FjPjU013620; Wed, 2 Aug 2006 08:45:25 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <44D0C895.8070301@freebsd.org> Date: Wed, 02 Aug 2006 08:45:25 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Jeremy References: <44CE199C.2020500@centtech.com> <17614.8289.134373.387558@bhuda.mired.org> <96b30c400607310847s1d2f845eo212b234d03f51e9a@mail.gmail.com> <17614.10982.499561.139268@bhuda.mired.org> <20060801072611.GA717@turion.vk2pj.dyndns.org> <20060801171150.GB3413@megan.kiwi-computer.com> <44CF8F1A.5090506@centtech.com> <20060801174048.GE3413@megan.kiwi-computer.com> <44D04797.1040201@freebsd.org> <20060802073340.GA713@turion.vk2pj.dyndns.org> In-Reply-To: <20060802073340.GA713@turion.vk2pj.dyndns.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Sparsifying Files (was Re: [PATCH] adding two new options to 'cp') X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Aug 2006 15:45:34 -0000 Peter Jeremy wrote: > As a general comment (not addressed to Tim): There _is_ a downside > to sparsifying files. How people use (or misuse) such a feature is just not my concern. I've not seen anyone on this thread suggest that such sparsification be done by default, and there are certainly rare situations where sparsification is useful. The tar implementation is about 95% system-independent file format work and 5% system-dependent hole mapping. The mapping process is the easy part. (And therefore, for me, the least interesting part.) A system call could make it accurate, but it's not enough code to fuss over either way. Tim