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 Date: Thu, 21 Apr 2005 16:28:23 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: findutils still broken Message-ID: <20050421202823.GB4887@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <042120052015 DOT 18583 DOT 426809E50001CC150000489722070009530A050E040D0C079D0A AT comcast DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <042120052015.18583.426809E50001CC150000489722070009530A050E040D0C079D0A@comcast.net> User-Agent: Mutt/1.5.8i On Thu, Apr 21, 2005 at 08:15:33PM +0000, Eric Blake wrote: >> Nevertheless, Cygwin does try only to set errno when there is an error. >> There are some cases where that isn't true but I didn't see any that >> referred to EISDIR. >> > >While I didn't find any EISDIR on success (yet), I did find the >following in 1.5.15: [l]stat() on /proc/registry/HKEY_CLASSES_ROOT sets >EBADF on success, and lstat() on >/proc/registry/HKEY_CLASSES_ROOT/\*/InfoTip sets ENOENT on success. I >originally wrote this program to discover that inode reporting in >readdir() is broken (to which you replied that fixing it would cause >too much of a slowdown), Yes, both Corinna and I had potential "fixes" (neither being a complete fix) for this in our sandboxes but they didn't make it into 1.5.15. Corinna got this working for >=XP which means that it wouldn't be right only on NTFS file systems on NT3.5, NT4, and NT2K. I just was going to get rid of the inode field entirely because, as you'd previously said, any well-designed software would adapt to the lack of that field. The end result was that neither of the changes got in. cgf -- 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/