Re: /bin/ksh as a default POSIX shell
>>"Herbert" == Herbert Xu <email@example.com> writes:
Herbert> And this is Debian where we have a policy that says #!/bin/sh scripts
Herbert> need to be POSIX compliant.
What policy says is:
The standard shell interpreter ``/bin/sh'' can be a symbolic link to
any POSIX compatible shell, if `echo -n' does not generate a newline.
 Thus, shell scripts specifying ``/bin/sh'' as interpreter should
only use POSIX features. If a script requires non-POSIX features from
the shell interpreter, the appropriate shell must be specified in the
first line of the script (e.g., ``#!/bin/bash'') and the package must
depend on the package providing the shell (unless the shell package is
marked `Essential', e.g., in the case of `bash').
 Debian policy specifies POSIX behavior for /bin/sh, but echo -n has
widespread use in the Linux community (including especially debian
policy, the linux kernel source, many debian scripts, etc.). This echo
-n mechanism is valid but not required under POSIX, hence this
explicit addition. Also, rumour has it that this shall be mandated
under the LSB anyway.
Ma Bell is a mean mother!
Manoj Srivastava <firstname.lastname@example.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C