2008.08.23 15:58 "Re: [Tiff] creating sparse files......", by Rogier Wolff
On Sat, Aug 23, 2008 at 10:54:54AM -0500, Bob Friesenhahn 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.
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)
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.
** 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