X-Spam-Check-By: sourceware.org X-IronPort-AV: i="4.09,452,1157324400"; d="scan'208"; a="7547315:sNHT29095216" Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: Re: cp command fails when copying from a network drive Date: Thu, 23 Nov 2006 11:52:49 -0000 Message-ID: From: "John Cooper" To: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id kANBrnb3014494 Corinna Vinschen wrote: > Can you please make an experiment? Just call `ls -i' a couple of times > on the same set of files and directories, and compare the inode numbers > returned. Probably the inode numbers differ between runs. Yes, the inode numbers do differ: $ ls -i v:/foo.txt 18446738026517403984 v:/foo.txt $ ls -i v:/foo.txt 18446738026635569488 v:/foo.txt $ ls -i v:/foo.txt 18446738026635114832 v:/foo.txt > I'm going to add a special case for this file system. Please give the > next developer's snapshot from http://www.cygwin.com/snapshots/ a try. OK, I'll look out for it. I've never installed a snapshot before - will it be sufficient to just take an updated cygwin1.dll (presumably in cygwin1-200611xx.tar.bz2) or do I also need an updated `cp' command? Thanks, --- John -- 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/