find bug?

[Sam Halliday]

hi there!

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).

i have tried passing all appropriate flags i know, such as -noleaf and i
also tried -fstype iso9660, -fstype ext3 (i know what this flag really
means... it was was just a shot in the dark it might do something..)

i feel slightly odd reporting this, since GNU find is such a well tested
and respected tool... i would doubt my own use of it over any possible
bug, but this time i have been left with no option.

is find parsing files as they appear on the hard-drive physically? can
it therefore be forced to rather look at an arbitrary FS in a
self-consist manner?

thanks in advance, and many apologies if i have wasted your time...
Sam
-- 
"Hi, Principal Skinner! Hi, Super Nintendo Chalmers!"
--Ralph Wiggum