On 4/1/06, Ross Wolin <[EMAIL PROTECTED]> wrote: > > Hi, > I'm having a problem using cygwin's find on WinXP. It works fine when I > run it on a local drive, but when I run it on my network drive, it tells me > directories don't exist, i.e.
What about plain files? Do the things that apparently don't exist actually exist? Is there a difference in the cases of the names? > V:\>find > . > ./mp3 > find: ./mp3: No such file or directory Can you reference ./mp3 (spelled exactly like that, with the leading dot-slash) from the same working directory? > the network drive is on a FreeBSD server, and is a Samba drive. I haven't got access to FreeBSD-* or to Cygwin, so I probably won't be able to reproduce this problem. You might actually have more luck asking on the Cygwin mailing list, because they're familiar with all the funny things that have to be done to make Cygwinlook like Unix. Does the problem happen if you run find on the local disk of the Cygwin box? What about if you run find against a Samba sever running something other than FreeBSD, or if you run it against an installation of Samba with the default configuration or a different version of Samba? Basically, what I'm trying to ask here, is for you to change the components of the problem in order to try to either localise the problem or to more specifically identify the components that are having an unfortunate interaction. > running find version 4.3.0. When I ran one of the older 4.2.x versions, I > got the inode changed problem others have mentioned on the web, when using > the network share. Is there more information I can give you to help > debug > the problem? See above for some ideas. If strace or ltrace work on Cygwin, those might provide useful diagnostics. Also, try asking for help on the Cygwin mailing list. James. _______________________________________________ Bug-findutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-findutils
