Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262848AbTKTTMQ (ORCPT ); Thu, 20 Nov 2003 14:12:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262901AbTKTTMQ (ORCPT ); Thu, 20 Nov 2003 14:12:16 -0500 Received: from mail.enyo.de ([212.9.189.167]:37137 "EHLO mail.enyo.de") by vger.kernel.org with ESMTP id S262848AbTKTTMP (ORCPT ); Thu, 20 Nov 2003 14:12:15 -0500 Date: Thu, 20 Nov 2003 20:12:09 +0100 To: Jesse Pollard Cc: Valdis.Kletnieks@vt.edu, Daniel Gryniewicz , linux-kernel mailing list Subject: Re: OT: why no file copy() libc/syscall ?? Message-ID: <20031120191209.GA9859@deneb.enyo.de> References: <1068512710.722.161.camel@cube> <03111209360001.11900@tabby> <20031120172143.GA7390@deneb.enyo.de> <03112013081700.27566@tabby> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <03112013081700.27566@tabby> User-Agent: Mutt/1.5.4i From: Florian Weimer Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 848 Lines: 20 Jesse Pollard wrote: > > > > > int sys_copy(int fd_src, int fd_dst) > > The default attributes in the new location might be less strict than the > > attributes of the source file. > > So what. the user was authorized to open the input file. The user was > authorized to open the output file. A file copy should be possible remotely > since the equivalent implementation of a local read/write loop would > accomplish the same thing. The potential for race conditions worries me. However, the questions you gave are more fundamental and may be enough to kill this idea (if it wasn't already dead)... - 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/