"whereis" versus "type"

[Michael ODonnell]

As an aside I'll mention that if you're using bash you
can ask it directly what it thinks a certain verb (eg.
"ethereal") means, thus:

   # type ethereal
   ethereal is /usr/bin/ethereal

...which gives me the exact answer to the question I had
in mind: "what will you run when I give this command?"
Further, since "type" is processed by bash itself it
knows about shell functions and aliases, something that
"whereis" (a separate app) rarely if ever gets right:

   # whereis l
   l:

   # type l
   l is aliased to `ls -aCF --color=no'