Messages in this thread | | | Date | Thu, 20 Nov 2003 18:21:43 +0100 | Subject | Re: OT: why no file copy() libc/syscall ?? | From | Florian Weimer <> |
| |
Jesse Pollard wrote:
> > > int sys_copy(int fd_src, int fd_dst) > > > > Doesn't work. You have to set the security attributes while you open > > fd_dst. > > Why? the open for fd_src should have the security attributes (both locally > and in the file server if networked). Opening fd_dst should SET the security > attributes desired (again, locally and in the target fileserver).
The default attributes in the new location might be less strict than the attributes of the source file.
If sys_copy() is just an API to introduce a new copy-on-write hard link, these problems disappear. They are only relevant if sys_copy() is intended to be a generic "copy that file" interface. - 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/
| |