Date: Wed, 02 Aug 2006 04:48:07 +0200 From: Ivan Voras <ivoras@fer.hr> To: freebsd-hackers@freebsd.org Subject: Sparsifying Message-ID: <eap3p4$7f2$1@sea.gmane.org> In-Reply-To: <p0623090cc0f5af237e7c@[128.113.24.47]> 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> <ean95a$e1u$1@sea.gmane.org> <p06230908c0f53813965d@[128.113.24.47]> <20060801171912.GC3413@megan.kiwi-computer.com> <p06230909c0f598682a82@[128.113.24.47]> <20060802001756.GB6671@megan.kiwi-computer.com> <p0623090cc0f5af237e7c@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
Garance A Drosehn wrote: > I *thought* what this thread was asking was for someone > to add some new option to `cp', where that new option It's a thread about several options to cp. > would do the above. But I was wrong with that, and > apparently people would be happy with a new option which > says "sparse-ify the file". Are you referring to the inablity to distinguish files with intentional NUL bytes and sparse files? Because of that, "copy sparse files as sparse files" and "sparsify files" are the same operation.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?eap3p4$7f2$1>