On Sun, May 03, 2009 at 04:01:12AM -0400, Christoph Hellwig wrote: > On Sat, May 02, 2009 at 11:15:01PM -0700, Joel Becker wrote: > > int reflink(const char *oldpath, const char *newpath); > > > > The reflink(2) system call creates reference-counted links. It creates > > a new file that shares the data extents of the source file in a > > copy-on-write fashion. Its calling semantics are identical to link(2). > > Once complete, programs see the new file as a completely separate entry. > > Just send this as a manpage to Michael, no need to duplicate a > pseudo-manpage in the kernel tree. The manpage style was just a convenient way to organize my thoughts. The goal was to document the behavior of reflink() for implementors. If the pseudo-manpage doesn't work, perhaps I'll try some other form. Joel -- Life's Little Instruction Book #337 "Reread your favorite book." Joel Becker Principal Software Developer Oracle E-mail: joel.becker@xxxxxxxxxx Phone: (650) 506-8127 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
