X-Spam-Check-By: sourceware.org From: ericblake AT comcast DOT net (Eric Blake) To: Danilo Turina , cygwin AT cygwin DOT com Subject: Re: Call for testing Cygwin snapshot Date: Thu, 27 Apr 2006 13:27:02 +0000 Message-Id: <042720061327.212.4450C6A60001E0B3000000D422073007930A050E040D0C079D0A@comcast.net> X-Mailer: AT&T Message Center Version 1 (Apr 11 2006) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 > > Another set of tests is to use the experimental coreutils-5.94-5. > > Doing/bin/pwd inside a directory on the strange filesystem stress tests > > d_ino (I already know that on ClearCase (MVFS), /bin/pwd fails inside of > > versioned directories, such as ccase/foo@@/main/, since ClearCase refuses > > to list foo@@ in a readdir of ccase, but that is not cygwin's bug). And > [...] > > I tried /bin/pwd and pwd in a versioned directory > (.../business@@/main/...) and it works. Do you mean that it doesn't work > with the current snapshot or with the current stable version? Which test > exactly fails? If you are using 5.94-5, then you are necessarily using a snapshot, and /bin/pwd would fail inside the versioned directory because I compiled it to use readdir() instead of getcwd(), and clearcase readdir() intentionally fails to list buisiness@@ when listing its parent directory. But coreutils 5.94-1 (and the eventual 5.94-6) stick with getcwd(), so that you should have no problems from inside a Clearcase versioned directory. And just to be sure, I will repeat my tests when I am at work today and have access to a clearcase drive, in case my claims about /bin/pwd were not quite accurate after all. -- Eric Blake volunteer cygwin coreutils maintainer -- 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/