On Sunday 09 December 2001 13:35, Pavel Machek wrote:
> > 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.
A filesystem with support of COW files would be *extremely* useful,
especially when writes trigger COW on block level, not file-by-file.
And it will definitely need in-kernel copyfile()/cowlink()/whatever name you
> > 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.
-- vda - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:17 EST