Messages in this thread | | | Date | Thu, 20 Nov 2003 22:49:53 +0100 (CET) | From | Maciej Zenczykowski <> | Subject | Re: OT: why no file copy() libc/syscall ?? |
| |
> It is, though. If you run out of space copying a file, you know it when > you're copying. Applications don't usually expect to get out-of-space > errors while overwriting something in the middle of a file.
What about sparse files?
> In effect, your free space and your used space add up to greater than > the capacity of the disk. An application that checks for free space > before doing something would be fooled into thinking there is more free > space than there really is. How can an application find out in advance > that a file that it's about to modify (without appending anything to the > end) is going to need more disk space?
I don't think it can do that already now with sparse files, can it?
Cheers, MaZe.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |