Compare files?

I'm looking for a way to make sure that the contents of two folders are exactly identical. I search the forum and google, and I saw a few ways that sound like they check that the filenames are the same in both directories, but don't actually compare the files themselves to be bit-for-bit identical (though I could be wrong in my understanding of what they're doing).

Do you know of a program or unix command that'll do a bit-for-bit file comparison of all the files in 2 folders?

 

Will it? Huh. In my quick skimming of the google results for that command, I got the impression that it was just checking the file names and directory locations, rather than doing a bit-for-bit comparison. Hmmm...

*goes to check google results again*


EDIT: Well, you were right, I was wrong. There goes my reading comprehension grade! Doh!

 

Thanks so much. Can you also just give me a quick non-techie example of how to properly execute a diff comparison of two folders' contents? Do I simply write this?

Code:

diff folder_A folder_B   

 

Thanks a bunch!

EDIT: And drag-n-drop terminal command file locations FTW!!!

 

Hah! Cool! I'm glad I could help you back in return!

 

Oh, one more thing, I just want to check how to do the sub-directories flag correctly. Would it go like this?

Code:

diff folder_A folder_B --recursive

 

Ah, thanks. I'm glad I asked.

It's a triple help win!

 

*hug*

*manly snicker*

 

Okay Queso (or anyone else), here's a little bit of a deeper question. I've been copying files onto my hard drive from aging CD-Rs so I can preserve my data, and diff recursive has been working beautifully to make sure I'm getting perfect file copies off of my CD-Rs. However, now I've come across a damaged CD-R. So I copied all of the files that the Finder's copy function didn't puke on, and now I want to use diff to see if all the files that transfered over without an error alert did, in fact, actually come across intact.

The problem now is that when I run diff, it terminates as soon as it gets to a file that the optical drive returns with an I/O error. So I can't check if the rest of the files after the damaged region were transfered over properly. And it's funny, because now is the situation where diff can really come in handy!

So the question is this: Is there a way to set diff to not terminate as soon as it reaches a file reporting with an I/O error?


p.s. I skimmed Diff's MAN page, but I am out of my league.