Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP
id AA2073 ; Thu, 25 Feb 93 10:10:43 EST
Xref: sserve comp.os.386bsd.development:24 comp.os.386bsd.bugs:15
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!apple!kaleida.com!conklin
From: conklin@kaleida.com (J.T. Conklin)
Newsgroups: comp.os.386bsd.development,comp.os.386bsd.bugs
Subject: Is fixing /bin/sh worthwhile?
Date: 23 Feb 93 17:46:03
Organization: Kaleida Labs, Inc., Mountain View, CA
Lines: 19
Message-ID: <CONKLIN.93Feb23174603@talisman.kaleida.com>
Reply-To: conklin@kaleida.com
NNTP-Posting-Host: talisman.kaleida.com
There are a number of bugs in ash (/bin/sh) that prevent proper
operation of shell scripts. I run into them frequently in Configure
scripts, c-news, etc.
I know many people have goto around these sort of problems by copying
bash to /bin/sh. But I'm attempting to fix the bugs. I fixed a
parsing bug last weekend, and I'm working on a quoting bug now.
Fixing all the bugs in ash may be a significant task. I really don't
want to invest the time to do so if it is going to be "officially"
replaced by bash, zsh, pd-ksh, or whatever in a future release.
--jtc
--
J.T. Conklin <jtc@wimsey.com> | Your source for floppy distributions
61 Crestwood Drive #18 | of the 386BSD OS and binaries
Daly City, CA 94015 | Send e-mail for complete product list
+---------------------------------------