Different Terminal operation methods

Question

I'm writing a report on my blog on some Terminal operations I performed recently to rescue a drive that was locked and with corrupt ACL. I want to get some things straight in my mind before I spread errouneous info.
When using a command like:
sudo cd /Volumes/Media
sudo find . -flags uchg -exec chflags nouchg {} \;
Which as I understand it will find all locked files on /Volumes/Media and unlock them
or using a command like:
sudo chflags -R nouchg /Volumes/Media
Which as I understand it will unlock ALL files recursively from the given directory, which effectively does the same thing as above.
What is the functional or operational difference between those two methods? Is there a safer or more preferable method?
Also, what is the difference between find . and find /
The Apple Discussions have been greatly helpful the past few weeks as I've learned more and more about how to get things done in Terminal. Thanks to all who share their knowledge here. I want to make sure I understand things fully before I make incorrect assumptions.
cheers
Adam

Answer 1

As as been explained above the
sudo cd ...
command is useless.  Frank Caggiano has explained why the sudo cd does not work as you think, but if you do not understand what he said, you need to come back and ask, as the concept of what happens iin a subprocess stays in a subprocess.  Things like your current working directory and shell variable and environment variable changes in a subprocess do not affect the originating shell (namely the one issuing the command prompt).  If you do not understant this, you will get tripped up again and again in the shell.
I'm assuming you have access to /Volume/Media, you cd without the sudo.  If for some reason you cannot cd to /Volume/Media, then you will need to take a totally different approach.
etresoft has mentioned that the 'find' approach will only modify the files that are locked, where as the chflags -R approach will blindly modify every file.  On the surface this may not appear to affect the end result, but the chflags -R approach will also change the ctime (Change Time) of every file, where as the 'find' approach will only change the ctime for the files that need changing.
The change to ctime may cause an incremental backup utility to backup every file in /Volume/Media instead of just the few files that have had their flags changed.
Also, what is the difference between find . and find /
. in Unix file systems is the current directory.  .. is the parent directory ../../ is the grandparent directory, etc...
/ is the top level of the boot file system.  From here every other file accessible via the operating system is somewhere under /
As has been explained, both . and / can be dangerous.  . is dangerous if you are not where you think you are, such as the case of using sudo cd no actually placing you where you think are going.  / is dangerous as depending on what you are doing with the 'find' command you can make some non-reversable file system modifications.
When playing with 'find' you might want to NOT include -exec until you absolutely know that the 'find' command you are creating spits out exactly what files you need to modify.  Or if you want to test with -exec, then use echo first
find . -flags uchg -exec echo chflags nouchg {} \;
where the echo command will display the chflags command that you plan to exeucte, but will not actually change anything.  You can then verify that the commands look good and the files being changed are what you expect.  You can later either remove the 'echo' or just pipe the command into sh
cd /Volumes/Media
find . -flags uchg -exec echo chflags nouchg {} \; | sudo sh