I am not sure why piping it to more does not work for you. But a simple solution would be to redirect the output to a file, and then page that. The following will redirect the standard output to a file, and the standard error will maintain the default, which is to display the error on the screen:
find . -iname '*something*' > myfile.out
more myfile.out
You will have to wait for find to complete to see everything though. If you want to get rid of those error messages entirely, and still have the non-error results go to that file:
find . -iname '*something*' > myfile.out 2> /dev/null
Each time you run this, myfile.out will be overwritten. This redirection is standard with the shell and can be used with most commands. Here is a little tutorial on redirection, it is worth learning.
The Other Examples:
With 2>&1 , standard error (stderr) is being redirected to stdout, so both end up getting piped to more. With 2> /dev/null you are sending them to special device which is basically a black hole ( aka the bit bucket). With *nix, devices are represented as a files.
lessis more. – Nerdling Nov 2 '09 at 20:08