Well you're right. My original line was:

#!/bin/ksh.

However, when I checked the directory it didn't exist. But QSH was
there. So I changed the line to:

I have never agreed with that error message (wouldn't "/bin/ksh not found"
have been more accurate and more helpful?) but the origins of unix have some
strange turns. This one's history I haven't tried to research. I can say
that the same anomaly exists in SunOS, AIX, HP-UX and Linux. That just
about covers it. :)

Anyway, glad I could help.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"It is easier to fight for one's principles than to live up to them."
-- Alfred Adler




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.