> I recently tried to compile a small C proggy with gcc, and, while it
> compiles fine, anytime I try to run it, I get a
> 
>         a.out:command not found
> 
> even though I can see the file, rename it, and it shows up with ls -F as a
> binary executable....
> 
> I thought maybe this was permission related, but chmod 777 a.out didn't help.

Nope.  It's because you don't have '.' in your path.  If you want the
DOSsy behavior, put '.' in your path.  But I'm warning you, it's a bad
idea to put '.' at the top of path, and it's even worse to have '.' in
the root's path.