On Sun, 16 Sep 2007, Shawn Walker wrote: > The people that created this problem are the idiots that put > #!/bin/sh at the top of their script and assume that means bash, > when it obviously isn't.
Exactly what I'm talking about Shawn. And I would have agreed with you up to five or six years ago. But the world has changed. The choice today is whether to go with that change or try to lead it in a different direction. IME the latter approach requires a large market share. Otherwise, decrease compatibility before attaining minimum mindshare, is certain to fail. > That's one of the reasons everyone at the company I work at is > required to specifically indicate which shell they're using via > #!/bin/ksh #!/bin/sh #!/bin/bash, etc. Since the scripts may be > run on other systems... And what about those systems that do not install bash, ksh, ... in /bin? Or are the other systems you're referring to managed by the same company writing the scripts? Bottom line, today as in the past, if you're writing for cross-platform compatibility there is no option other than "#!/bin/sh". -- Roger Marquis Roble Systems Consulting http://www.roble.com/ _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
