On 3/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>No it is not. You're wrong. Put /usr/bin/ksh into a SMF script and it >will not be executed. Have you actually tried this?
Yes. It will not work.
SMF calls "execve" and unless there's something wrong with the environent, like trying a ksh script before mounting /usr, any interpreter should work fine. Or are you taking about /etc/rc?.d/* legacy scripts? Those are, as before, strictly fed to /bin/sh
Why? Why can't you use /usr/bin/ksh or /usr/xpg4/bin/sh as interpreter for all the scripts.
>It will always use /bin/sh and ignores what you use as #! line in a >script. Files ending in .sh will be inlined (which is good since you >can set environment variables without using /etc/profile. SMF can't do >that). Ah, you are talking about legacy scripts.
I am talking about SMF scripts and /etc/init.d scripts.
>No, I blame Solaris for not honoring the POSIX standard. It does confirm to POSIX;
Is there any certification?
it's just that you don't undersand the finesses of POSIX (and the freedoms) (POSIX says there needs to be a POSIX shell; not where it is)
Is there any other operating system which uses this finesses/freedom as justification to make /bin/sh a standard-violating shell? Cheers, William -- @,,@ William James (\--/) [EMAIL PROTECTED] (.>__<.) GNU/Solaris hacker _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
