On Wed, Aug 01, 2007 at 10:46:32AM -0300, Henrique de Moraes Holschuh wrote:
> On Wed, 01 Aug 2007, Pierre Habouzit wrote:
> > debconf is definitely not the proper way. Using alternatives is.
>
> Remember you are dealing with essential stuff.
>
> /bin/sh must *NEVER*, not even for a milli-second, be unavailable. You are
> only to change it using atomic operations, and when you are *completely*
> sure it will work after the operation completes.
agreed. In fact, after some pondering, I think /bin/sh should be dash,
because it's fast, and isn't crippled wrt nss modules (allowing /var to
be unmounted when nscd is used e.g.). I don't see a valid reason for the
user to chose what lies behind /bin/sh. If he wants to use his favourite
sh shell features in his scripts, he shall use #!/bin/favouritesh and
done.
I can't care less if /bin/sh is dash, posh or mksh. It just has to be
a posix shell, _and_ a fast one. That rules bash out[1], that's all I
can tell.
[1] I know bash isn't _That_ slow, it's very slow to start, hence is a
bad choice for a /bin/sh that often interprets very short lived
scripts.
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
Attachment:
pgpP1N9S7tRMU.pgp
Description: PGP signature