Messages in this thread | | | Date | Sun, 9 Dec 2001 15:35:23 +0000 | From | Pavel Machek <> | Subject | Re: File copy system call proposal |
| |
Hi!
> I would like to propose implementing a file copy system call. > I expect the initial reaction to such a proposal would be "feature > bloat" but I believe some substantial benefits can be seen possibly > making it worthwhile, primarily the following: > > Copy on write:
You want cowlink() syscall, not copy() syscall. If they are on different partitions, let userspace do the job.
> Will many other users benefit from these features? Will implementing > them (especially copy on write) cause an excessive addition to the code > of the kernel?
Hmm, I have almost 20 different copies of kernel on my systems.... Yep it would save me a *lot* of space. Pavel -- Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt, details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
- 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/
| |