Date: Mon, 17 Apr 2000 01:10:15 -0700 From: "David O'Brien" <obrien@freebsd.org> To: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca> Cc: freebsd-arch@freebsd.org Subject: Re: Shells V2 Message-ID: <20000417011015.A3064@dragon.nuxi.com> In-Reply-To: <200004160031.e3G0Vt302555@cwsys.cwsent.com>; from Cy.Schubert@uumail.gov.bc.ca on Sat, Apr 15, 2000 at 05:31:26PM -0700 References: <200004160031.e3G0Vt302555@cwsys.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Apr 15, 2000 at 05:31:26PM -0700, Cy Schubert - ITSD Open Systems Group wrote: > > With commit of tcsh, I'd like to raise another question. Are there any > plans to replace sh with bash? No. > Granted they're not 100% compatible, This is a big problem. We don't have C-shell scripts in the base system (Ok, one non-critical one). However, /etc is full of critical Bourne shell scripts. > I still think it might be a good idea to replace sh with bash. The Bash license would also prevent it, if bash2 were 100% compatible with ash (/bin/sh). I'd bring in the real Korn Shell way before I'd bring in Bash. Tcsh is not a new shell, it is just a newer version of the 4.4BSD C-shell. > If replacing sh with bash is unpalatable for some or most of us, what > about putting bash2 in the base system along side of sh? 3. GNU Public Virus Licensed. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000417011015.A3064>