X-Spam-Check-By: sourceware.org
To: cygwin@cygwin.com
From: Eric Blake <ebb9@byu.net>
Subject:  Re: cygwin copy problems usb 2.0
Date: Thu, 3 Aug 2006 20:00:51 +0000 (UTC)
Lines: 17
Message-ID:  <loom.20060803T214608-824@post.gmane.org>
References:  <080320061908.15481.44D24998000AE51600003C7922064244130A050E040D0C079D0A@comcast.net> <20060803192135.GD5300@calimero.vinschen.de>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:

> 
> Does cp already use ftruncate?

Yes, when copying from one regular file to another, cp (and mv and install, 
which share the same code for file copies) uses ftruncate.  But it currently 
only uses it for creating holes at the tail end of sparse files, relying on 
lseek for holes in the middle.  It currently does not use posix_f
{allocate/advise), although I think such a patch would be useful independently 
of cygwin.

-- 
Eric Blake





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/