Re: Several reasons why debian should not use bash for /bin/sh
I was just getting ready to forward this to debian-devel (-:
I set my sh link to point to ash last night. All seems well so far.
Will reboot when I get home. I have had one problem. A configure
script from a program I downloaded called /bin/sh, yet it declared a
function. To my knowledge bourne does not support functions. Changing
the #! line to call bash instead worked.
I would like to second Chris on this one. Low memory machines do still
exist and having >64megs of RAM is not an excuse to squander memory.
Supporting shells like ash would help our 486 friends as well as
machines with a great deal of scripting occuring.
As to the ksh shell not being Bourne compliant I agree with you Chris in
theory. However I have seen scripts work in sh and bash, but not in ksh
(and yes sh was its own shell and not a link to bash). This may have
changed -- this was over a year ago.
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: