Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!dog.ee.lbl.gov!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: ash (was: Re: Elm fixed easily for 386bsd)
Message-ID: <1993Mar15.214055.9197@fcom.cc.utah.edu>
Sender: news@fcom.cc.utah.edu
Organization: Weber State University (Ogden, UT)
References: <CONKLIN.93Mar3140546@ngai.kaleida.com> <6493@krafla.rhi.hi.is> <C3oJnI.H8s@sugar.neosoft.com>
Date: Mon, 15 Mar 93 21:40:55 GMT
Lines: 35
In article <C3oJnI.H8s@sugar.neosoft.com> karl@NeoSoft.com (Karl Lehenbauer) writes:
>In article <6493@krafla.rhi.hi.is> adamd@rhi.hi.is (Adam David) writes:
>>I'm currently working on a backquote/quoting bug that is causing
>>problems in c-news' subst script. Hopefully, I can finish it off
>>tonight.
>
>Note that "bash" does not suffer from this problem. And with it as /bin/sh
>cnews pretty much compiles and runs.
There are two problems with this:
1) bash isn't exactly sh compatable. ash will be once all the bugs
are all (mostly) fixed.
2) bash is GPL'ed. Not to get into a war about "The Way It Should Be",
"The Way It Is" allows us to produce a binary-only system without
sources to everything but the developement system, arguably a
piece that can be left out of an end-user system. Including bash
would break this.
As far as I'm concerned, ignoring the bugs in ash simply because bash
exists is not the way to go.
Terry Lambert
terry@icarus.weber.edu
terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
--
-------------------------------------------------------------------------------
"I have an 8 user poetic license" - me
Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------