Re: OT: why no file copy() libc/syscall ??

[Nick Piggin]

Robert White wrote:

> (Among the other N objections, add things like the lack of any sort of
> control or option parameters)
> ...
> N += 1: Sparse Copying (e.g. seeking past blocks of zeros)
> N += 1: Unlink or overwrite or what?
> N += 1: In-Kernel locking and resolution for pages that are mandatory
> lock(ed)
> N += 1: No fine-grained control for concurrency issues (multiple writers)
>
> Start with doing a cp --help and move on from there for an unbounded list of
> issues that sys_copy(int fd1, int fd2) does not even come close to
> addressing.

To be fair, sys_copy is never intended to replace cp or try to be
very smart. I don't think it is semantically supposed to do much more
than replace a read, write loop (of course, the syscall also has an
offset and count).

sparse copying would be implementation dependant. If cp wanted to do
something special it would not use one big copy call. I think unlink
/ overwrite is irrelevant if its semantically a read write loop.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/