Re: find bug?

[Sam Halliday]

Bob Proulx wrote:
> > i have recently been trying to write a simple script in order to
> > verify a burnt CD, however i ran into this problem... GNU find seems
> > to parse an iso9660 FS differently to others (at least ext3).
> Find looks at filenames.  What does 'ls' say?  Find would be seeing
> the same information.  If you (and 'ls') can't see the files then
> 'find' can't see the files either.

im very sorry.. i didnt make myself entirely clear... by 'parsing' i
mean, 'looks at and displays the file in a different order'. ls will
always organise the files alphabetically (or whatever i tell it to), but
find seems to not be consistent in the parsing 'order' of files on these
2 filesystems, ext3 and iso9660

i can make an example to do this if you require one, which would create
a whole load of files and then 'find' the tree under ext3 and then under
iso9660... im sure you could make a test case easily enough, attached is
output i prepared earlier.

there are 2 files, "hd.md5sum" is the command
find . -type f -exec md5sum '{}' ';'
under an ext3 FS, and "cd.md5sum" is the same command under iso9660. a
simple diff will show that the order of the files is different in each
case... and in my case, this means i am unable to compare md5sum lists
of 2 trees to see what has changed...

i have also tried this with -noleaf incase that was the cause of the
problem.

hope this report was more clear :D

thanks in advance!
Sam
PS: sorry for the larger than normal posting

hd.md5sum
Description: Binary data

cd.md5sum
Description: Binary data