So, that's a problem with the script writer saying "#!/bin/sh" when his/her script won't actually run under sh. But I see now what Stewart was arguing against.
If "sh" is always bash for most people, that causes incorrectly written shell scripts, whoever's fault it is.
Older versions of bash would limit itself to bourne functionality when run as sh. Does the newer version not do that anymore?
-- "The other teams could make trouble for us if they win." --Yogi Bera -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
