Date: Wed, 02 Aug 2006 08:45:25 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Peter Jeremy <peterjeremy@optushome.com.au> Cc: freebsd-hackers@freebsd.org Subject: Sparsifying Files (was Re: [PATCH] adding two new options to 'cp') Message-ID: <44D0C895.8070301@freebsd.org> In-Reply-To: <20060802073340.GA713@turion.vk2pj.dyndns.org> References: <44CE199C.2020500@centtech.com> <17614.8289.134373.387558@bhuda.mired.org> <96b30c400607310847s1d2f845eo212b234d03f51e9a@mail.gmail.com> <17614.10982.499561.139268@bhuda.mired.org> <ealpn1$lan$1@sea.gmane.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44D0C895.8070301>