Return-Path: <tiff-bounces@lists.maptools.org>
Delivered-To: info@awaresystems.be
Received: (qmail 12191 invoked from network); 23 Aug 2008 16:01:02 -0000
Received: from cheryl.telenet-ops.be ([195.130.136.3])
          (envelope-sender <tiff-bounces@lists.maptools.org>)
          by angelia.telenet-ops.be (qmail-ldap-1.03) with SMTP
          for <info@awaresystems.be>; 23 Aug 2008 16:01:02 -0000
Received: from vijay.telenet-ops.be (vijay.telenet-ops.be [195.130.136.9])
	by cheryl.telenet-ops.be (8.13.1/8.13.1) with ESMTP id m7NG11nZ025138
	for <info@awaresystems.be>; Sat, 23 Aug 2008 18:01:01 +0200
Received: from localhost (localhost.localdomain [127.0.0.1])
	by vijay.telenet-ops.be (Postfix) with SMTP id CFEE860004
	for <info@awaresystems.be>; Sat, 23 Aug 2008 18:01:01 +0200 (CEST)
Received: from crotus.telenet-ops.be (crotus.telenet-ops.be [195.130.132.38])
	by vijay.telenet-ops.be (Postfix) with ESMTP id BA9ED60002
	for <info@awaresystems.be>; Sat, 23 Aug 2008 18:01:01 +0200 (CEST)
Received: from duke.maptools.org (r153.dmsolutions.ca [209.217.116.153])
	by crotus.telenet-ops.be (Postfix) with ESMTP id 57C9FC
	for <info@awaresystems.be>; Sat, 23 Aug 2008 18:01:01 +0200 (CEST)
Received: from duke.maptools.org (duke.maptools.org [127.0.0.1])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id m7NFww0f025057;
	Sat, 23 Aug 2008 12:00:15 -0400
Received: from abra2.bitwizard.nl (dtp.xs4all.nl [80.101.171.8])
	by duke.maptools.org (8.12.11/8.12.10) with SMTP id m7NFwtZU025054
	for <tiff@lists.maptools.org>; Sat, 23 Aug 2008 11:58:55 -0400
Received: (qmail 29041 invoked by uid 1000); 23 Aug 2008 17:58:54 +0200
Date: Sat, 23 Aug 2008 17:58:54 +0200
From: Rogier Wolff <R.E.Wolff@bitwizard.nl>
To: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
Subject: Re: [Tiff] creating sparse files......
Message-ID: <20080823155854.GA28115@bitwizard.nl>
References: <20080822085634.GA21294@bitwizard.nl>
	<Pine.SOC.4.64.0808220936280.1110@freddy.simplesystems.org>
	<20080822162748.GB29030@bitwizard.nl>
	<Pine.SOC.4.64.0808221131320.1110@freddy.simplesystems.org>
	<20080822165232.GE29030@bitwizard.nl>
	<Pine.SOC.4.64.0808221249090.1110@freddy.simplesystems.org>
	<20080823150831.GE18815@bitwizard.nl>
	<Pine.SOC.4.64.0808231051400.1110@freddy.simplesystems.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.SOC.4.64.0808231051400.1110@freddy.simplesystems.org>
Organization: BitWizard.nl
User-Agent: Mutt/1.5.13 (2006-08-11)
Cc: tiff@lists.maptools.org, Rogier Wolff <R.E.Wolff@bitwizard.nl>
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=subscribe>
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org
X-SpamCatcher-Score: 50 [XX]

On Sat, Aug 23, 2008 at 10:54:54AM -0500, Bob Friesenhahn wrote:
> On Sat, 23 Aug 2008, Rogier Wolff wrote:
> >
> >>For example,
> >>Apple OS-X's HFS+ does not support holes.
> >
> >Weird. So, will my suggested code fail? No.
> 
> OS-X's HFS+ will simply consume the space with zeros.
> 
> >>Windows FAT type
> >>filesystems (still very much in use in millions of systems/devices) do
> >>not support holes.
> >
> >Correct. But will my code fail? No. It does skip the copying of
> >"zeroes" from userspace into the kernel. Wether this will in fact
> >increase or decrease perfomance when all things are added up, I don't
> >know.
> 
> The code may very well fail.

Nope. 


> >It is likely that you don't know that the posix specifications are
> >pretty clear about this.
> >
> >If I program
> >
> >	main (int argc, char **argv)
> >	{
> >		int a;
> >		int b;
> >		a = 3;
> >		b = 5;
> >		printf ("%d\n", a+b);
> >	}
> >
> >the output should be "8". This is because I used standard features of
> >a standard programming language. Opening and writing files goes a bit
> 
> You are communicating with someone who has used and programmed "unix" 
> for twenty years now.  The above was not called for.

Same here. So?

You say: "The code may very well fail". How can I provide arguments
against that? There are standards that imply the answer "8" from the
short program above, and correct results from the code I suggested. 

	Roger. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
**    Delftechpark 26 2628 XH  Delft, The Netherlands. KVK: 27239233    **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. 
Does it sit on the couch all day? Is it unemployed? Please be specific! 
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ
_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
