X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Eric Blake <ebb9 AT byu DOT 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 DOT 15481 DOT 44D24998000AE51600003C7922064244130A050E040D0C079D0A AT comcast DOT net> <20060803192135 DOT GD5300 AT calimero DOT vinschen DOT de>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT 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/

- Raw text -