Date: Tue, 20 Jul 2004 19:57:39 +0200 From: Matthias Buelow <mkb@mukappabeta.de> To: Peter Jeremy <PeterJeremy@optushome.com.au> Cc: current@freebsd.org Subject: Re: NEW TAR Message-ID: <16637.23827.578767.763759@moghedien.mukappabeta.net> In-Reply-To: <20040720081051.GB3001@cirb503493.alcatel.com.au> References: <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> <40FC9FC2.8050400@kientzle.com> <20040720081051.GB3001@cirb503493.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Jeremy writes:
>Actually, it's not possible to accurately determine the holes in a
>file by reading it - you can't differentiate between a hole and a
>allocated block of zeroes. What you need is a (new) syscall that
but that's the point, isn't it. if you get a larger block of zeroes,
you seek forward that number in the output file, and let the
filesystem create (any) holes.
>invokes a new VOP_... and returns a bitmap of allocated blocks. This
>would be non-trival unfortunately.
this is completely unnecessary and wouldn't work across filesystems
anyways.
--
Matthias Buelow; mkb@{mukappabeta,informatik.uni-wuerzburg}.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16637.23827.578767.763759>