Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 20 Dec 2001 10:07:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 20 Dec 2001 10:07:00 -0500 Received: from bacon.van.m-l.org ([208.223.154.200]:14979 "EHLO bacon.van.m-l.org") by vger.kernel.org with ESMTP id ; Thu, 20 Dec 2001 10:06:54 -0500 Date: Thu, 20 Dec 2001 10:06:42 -0500 (EST) From: George Greer X-X-Sender: To: David Woodhouse cc: "linux-kernel@vger.kernel.org" Subject: Re: File copy system call proposal In-Reply-To: <3794.1008858687@redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 20 Dec 2001, David Woodhouse wrote: >jakob@unthought.net said: >> Take a look at Win32, they have it. > >Which is partly why when you want to copy a large file on an SMB-exported >file system, the client host doesn't have to actually read it all and write >it back across the network - it can just issue a copyfile request. What does a copy system call have to do with the file server program being smart enough to do a copy locally? You can't do it with FTP (or at least the ftpd I have) but it's certainly not because read()+write() are insufficient. -George Greer - 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/