find.exe from the latest port of FindUtils 4.2.20-1 fails when
invoked on a directory from another drive. Here's an
D:\usr\bin> find c:/Temp d:/foo
D:\USR\BIN\FIND.EXE: /usr/bin: No such file or directory
D:\usr\bin is the directory where I invoked Find, so I'm
guessing that perhaps, after it exhausted all the files in
C:\Temp, Find tries to chdir back to where it started, and
that fails because it doesn't change drives correctly, or
because it looks for /usr/bin instead of d:/usr/bin.
This bug makes Find unusable as the tool for producing
locatedb.dat, the database for Locate, on systems with
more than one drive, because "find c:/ d:/ e:/" is typically
the first part of a pipeline run by the updatedb script on
such systems. Since Find fails after it finishes with the first
drive, the resulting Locate database includes only a small
part of files that are actually available on the machine.