Off-topic

[Will Ware]

Ivan Van Laningham (ivanlan at callware.com) wrote:
> Why don't #! scripts seem to work anymore?  #!/usr/bin/python and
> #!/usr/bin/perl scripts don't work.  Error is

> bash:  ./h2n:  No such file or directory

This usually means that bash can't find the executable mentioned
in the first line of your script. On RH6.1 you should find python
in /usr/bin, but if you're seeing this message maybe something
happened to it. Just for yucks, type "which python", then it will
tell you where it expects to find python.

Since I sometimes run scripts on different machines, I've found
that using this first line works better:

#!/usr/bin/env python

This of course assumes that "env" is in /usr/bin, but that seems
to be a more consistent rule than finding python in /usr/bin.
-- 
 - - - - - - - - - - - - - - - - - - - - - - - -
Resistance is futile. Capacitance is efficacious.
Will Ware	email:    wware @ world.std.com