-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to [EMAIL PROTECTED] on 6/15/2006 4:32 AM: > Hi all, > > I had the cygdrive 'find' problem whereby the command cant traverse the > mounted drived under /cygdrive properly, as described in these posts: > > http://sourceware.org/ml/cygwin/2005-11/msg00772.html
This is already a known problem, and another already known solution is to use a recent cygwin snapshot. In fact, if you were to use 4.3.0's oldfind, it would have the same problem as 4.2.27's find. > It was a major pain because it also broke updatedb. I just forced the > upgrade from 4.2.27 to 4.3.0 and now the problem is fixed, so there you > go! The only reason I have not made 4.3.0 the current version is because it is alpha quality upstream, and 4.2.27 depends on cygwin 1.5.19; making 4.3.0 current would leave no fallback for users trying to revert to cygwin 1.5.18. But as soon as cygwin 1.5.20 comes out (whenever that might be), my story will change, since I will no longer have to worry about 1.5.18 compatibility. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] volunteer cygwin findutils maintainer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEkVR684KuGfSFAYARAq3DAJ49gNu5MYuDSrqcOjXBkCInly4rSgCfUBnm z2wAO8xbk7hBpiKPXICAFqA= =28f6 -----END PGP SIGNATURE----- -- 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/
