Slightly off-topic and moderately unpopular: find(1) doesn't quite well fit into the Unix userland. It starts with the syntax: multiletter options (POSIX calls them operands though), the $program $option(s) $file(s) order (compare the find's "do where what" vs natural -- like sed's or grep's -- "do what where"), and the overall purpose of the utility: it should construct a list of files/directories and match the given pattern. In its simplest form find(1) should work like this: % find regex path
"du -a | grep pattern" already does this. I may not understand find(1) though because my general use of the command (if I'm not du-a-grepping) only includes searching for files that match a specific pattern. -- caóc
