Oron Peled <[EMAIL PROTECTED]> writes: > The correctness of you assertion greatly depends on which "those" you mean. > Sunos (which was the dominant Unix throughout the 80's and the beginning > of the 90's) had /bin/csh as default. BTW, this explains how some parts > in the academic world got the weird idea of teaching scripting in > csh.
I thought Bourne sh was the installation default on SunOS, too. It certainly predates csh. However, csh was originally written by Bill Joy, if memopry serves, so it well may be that it was the default on SunOS. I'll trust your memory more than mine. Does the Single UNIX Specification mandate that Bourne sh be present on compliant systems? Google shows Wikipedia (http://en.wikipedia.org/wiki/Single_UNIX_Specification) as the first hit (rather than the SPec itself, curiously), and the article says so. I suspect that http://www.opengroup.org/onlinepubs/009695399/utilities/echo.html is the definitive document regarding echo. To quote: "Implementations shall not support any options." "It is not possible to use echo portably across all POSIX systems unless both -n (as the first argument) and escape sequences are omitted." "New applications are encouraged to use printf instead of echo." >> b) consider #!/bin/bash even for portable code (restricting it to >> systems with bash installed, of course). > > Hmmm... I disagree, but I'll leave it as a religious subject ;-) Hmmm... Consider the key word "consider" - maybe it's not so religious... ;-) -- Oleg Goldshmidt | [EMAIL PROTECTED] | http://www.goldshmidt.org ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
