nonsense words for files

[Guy Harris]

> This reminds me of my usual mistake -- under UNIX, create a program
> test.c, compile it using make into test, and try to execute it.
> You get no output very quickly, since test is part of the shell.
> Hard to debug, too, since you can't find another executable file
> in your PATH.

In the System V Release 2 shell, you can do "type test" which will tell you
what type of command "test" is (and, if it's an executable program or
script, what the full pathname is).  Useful for this kind of thing.

	Guy Harris