This is the mail archive of the
mailing list for the Cygwin project.
Re: AGAIN - cp: skipping file ... as it was replaced while being copied
- From: Ivan Dobrianov <cygwin-bo0 at dobrianov dot net>
- To: cygwin at cygwin dot com
- Date: Fri, 4 Apr 2008 15:23:48 -0400
- Subject: Re: AGAIN - cp: skipping file ... as it was replaced while being copied
OK - just for the record and in case this ever needs to be debugged,
here's the result.
I got the latest snapshot cygwin1-20080327.dll.bz2. It fixed the "cp
from network" problem, but created a strange issue with mounted
disks. Here it is.
Normally I have mounted c: and d: like this
mount c:/ /c; ls /c
mount d:/ /d; ls /d
so that /c and /d lead to the top-levels of c: and d: respectively. As
a result, I _normally_ have this:
/tmp > mount
C:\bin\cygwin\bin on /usr/bin type system (binmode)
C:\bin\cygwin\lib on /usr/lib type system (binmode)
C:\bin\cygwin on / type system (binmode)
c: on /c type system (binmode)
d: on /d type system (binmode)
Now, with the dev snapshot cygwin1.dll, all is well except that "ls
/d" seems to list /c and in fact "ls /<any_single_letter>" seems to
behave like "ls /c"! I can still see d: under "ls /cygdrive/d/", but
not under its mount point, which is /d/. Also, when I list /c I get an
error regarding not being able to open Documents\ and\ Settings. Strange!
So I reverted back to the original cygwin1.dll :-)
If there is any interest on the part of any cygwin developer in
pursuing this matter, I'd be happy to cooperate, but other than that
I'll leave it at that - at least for the near future.
>On Apr 3 20:35, Ivan Dobrianov wrote:
>> Hi and sorry for the clutter, but I can't figure it out!
>> I have this familiar situation when trying to copy from the network:
>> cp //walnetapp01/SRD/LegacyBugs/148000-148999/148708/some_file.txt ./
>> cp: skipping file `//walnetapp01/SRD/LegacyBugs/148000-148999/148708/some_file.txt', as it was replaced while being copied
>> Now, I looked through the mailing list archives and found two relevant threads on this subject, namely:
>> The thing is that neither of them ends up with a prescription of how to fix the problem :-)
>> In message 2006-11/msg00604.html, Corinna says:
>> 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.
>> Well, here I am in April 2008, with a fresh new Cygwin installation - I am assuming that by now this prblem whould have been resolved in the main branch. Am I wrong? Do I have to do anything special?
>The patch is in CVS, not in the latest release. You could try the
>latest developer snapshot from http://cygwin.com/snapshots/, but for the
>time being, there's no fix for the release itself. Note that snapshots
>are not made for production environments. Use at your own risk.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html