X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: cp command fails when copying from a network drive Date: Thu, 23 Nov 2006 16:41:24 -0000 Message-ID: <002001c70f1e$36c71240$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <20061123150302.GL8333@calimero.vinschen.de> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On 23 November 2006 15:03, Corinna Vinschen wrote: > On Nov 23 11:52, John Cooper wrote: >> Corinna Vinschen wrote: >> > Can you please make an experiment? Just call `ls -i' a couple of >> >> Yes, the inode numbers do differ: > > Yeah, that was expected. Thanks for confirming. > > I can't stop wondering what people thin when implementing "random" file > ids resp. inode numbers. Stuff like that should be reported back to > manufacturer *hint* *hint* We have a netapp here, and it doesn't do that at all. John, do you have the netapp 'SecureShare' software installed on the PC you're using? cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/