Not really... The standard synopsis for the find utility is:

Code:

find [−H|−L] path... [operand_expression...]

Find uses each given path operand as a root from which the operand-expression will be evaluated. If you name a regular file as a path operand, only that file will be evaluated (not the directory in which it resides). If you name a directory, it will evaluate that directory and all files in the file hierarchy rooted in that directory (unless part of the operand_expression limits the search.

When you invoke the command:

Code:

find /u05/*.fooo -print

the shell expands /u05/*.fooo to a list of matching files before find starts running. If you run the command:

Code:

find /u05 -name '*.fooo' -print

the find utility is expanding the *.fooo looking for matching files in and under /u05 and (in your example) prints:

Code:

/u05/xyz.fooo

Note that a common mistake for newbies is to invoke the above command without the quotes:

Code:

find /u05 -name *.fooo -print

If you're sitting in / when you execute that command in your example, it won't print anything. The shell will expand the *.fooo to abc.fooo (which you created in /) so the arguments find will see will be:

Code:

find /u05 -name abc.fooo -print

and /u05 contains xyz.fooo; but no file named abc.fooo.

And the command:

Code:

find /tmp /u05 "$HOME" -name '*.fooo'

with or without a -print primary, will print /u05/xyz.fooo and the names of any other files in /tmp and its subdirectories, /u05 and its subdirectories, and your home directory and its subdirectories with names that end with .fooo.