Subject: Re: OT: why no file copy() libc/syscall ??
From: David Woodhouse <dwmw2@infradead.org>
To: Jesse Pollard <jesse@cats-chateau.net>
Cc: "Ihar 'Philips' Filipau" <filia@softhome.net>,
       Davide Rossetti <davide.rossetti@roma1.infn.it>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
In-Reply-To: <03111007291500.08768@tabby>
References: <QiyV.1k3.15@gated-at.bofh.it> <3FAF7FC8.8050503@softhome.net>
	 <03111007291500.08768@tabby>
Content-Type: text/plain
Message-Id: <1068477550.5743.50.camel@hades.cambridge.redhat.com>
Mime-Version: 1.0
Date: Mon, 10 Nov 2003 15:19:11 +0000
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 701
Lines: 20

On Mon, 2003-11-10 at 07:29 -0600, Jesse Pollard wrote:

> > > sys_fscopy(...)
> 
> It is too simple to implement in user mode.

Is it? Please explain the simple steps which cp(1) should take in order
to observe that it is being asked to duplicate a file on a file system
such as CIFS (or NFSv4?) which allows the client to issue a 'copy file'
command over the network without actually transferring the data twice,
and to invoke such a command.

-- 
dwmw2

-
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/