From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263742AbTLAQgM (ORCPT ); Mon, 1 Dec 2003 11:36:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263752AbTLAQgM (ORCPT ); Mon, 1 Dec 2003 11:36:12 -0500 Received: from 34.mufa.noln.chcgil24.dsl.att.net ([12.100.181.34]:43762 "EHLO tabby.cats.internal") by vger.kernel.org with ESMTP id S263742AbTLAQgK (ORCPT ); Mon, 1 Dec 2003 11:36:10 -0500 Content-Type: text/plain; charset="CP 1252" From: Jesse Pollard To: David Lang , =?CP 1252?q?J=F6rn=20Engel?= Subject: Re: OT: why no file copy() libc/syscall ?? Date: Mon, 1 Dec 2003 10:20:18 -0600 X-Mailer: KMail [version 1.2] Cc: Nick Piggin , "Robert White \"'Florian Weimer'\"" , Valdis.Kletnieks@vt.edu, "'Daniel Gryniewicz'" , "'linux-kernel mailing list'" References: <20031127100217.GA9199@wohnheim.fh-wedel.de> In-Reply-To: MIME-Version: 1.0 Message-Id: <03120110201800.12834@tabby> Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thursday 27 November 2003 04:58, David Lang wrote: [snip] > actually thinking about it a bit more, did I make a stupid mistake and > think that the FD points at the beginning of the file when it really > points at the inode? if it points at the inode then the problems I was > refering to don't exist. Actually, it points to inode and offset in the file. The advantage this has is in the case of appending to a file... open the destination file, seek to the end, then copy. It also allows seeking some offset in the input file, then copying the rest of the file.