Messages in this thread | | | Date | Thu, 20 Nov 2003 15:44:16 -0500 | From | Timothy Miller <> | Subject | Re: OT: why no file copy() libc/syscall ?? |
| |
Justin Cormack wrote: > On Thu, 2003-11-20 at 19:08, Jesse Pollard wrote:
> If you really want a filesystem that supports efficient copying you > probably want it to have the equivalent of COW blocks, so that a copy > just sets up a few pointers, and the copy only happens when the original > or copied files are changed. > > But basically you wont get a syscall until you have a filesystem with > semantics that only maps onto this sort of operation.
This could be a problem if COW causes you to run out of space when writing to the file.
This could also be a benefit if, for whatever reason, you have lots of copies of the same file that you never change. But that sounds somewhat pointless to me.
- 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/
| |