Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!uxc!uxc.cso.uiuc.edu!uxg.cso.uiuc.edu!uicsrd.csrd.uiuc.edu!mcdaniel
From: mcdaniel@uicsrd.csrd.uiuc.edu
Newsgroups: comp.sources.d
Subject: Re: Bourne Again Shell?
Message-ID: <42400008@uicsrd.csrd.uiuc.edu>
Date: 11 Feb 89 06:06:00 GMT
References: <26563@teknowledge-vaxc.ARPA>
Lines: 22
Nf-ID: #R:teknowledge-vaxc.ARPA:26563:uicsrd.csrd.uiuc.edu:42400008:000:829
Nf-From: uicsrd.csrd.uiuc.edu!mcdaniel    Feb 11 00:06:00 1989


Summary: what is this "Bourne-again (groan) shell"?

> Paul's fixing job control and adding his tcsh editor.  ksh features
> will start arriving after stability is achieved.

Why didn't they just implement ksh from the start?  I would think it
easier and cleaner to do that than to aim at sh and then patch in
changes.

Will the Bourne-again shell (bash? :-) be a superset of ksh?  If so,
what extra features are envisioned?

--

             Tim, the Bizarre and Oddly-Dressed Enchanter

Center for      |||  Internet, BITNET:  mcdaniel@uicsrd.csrd.uiuc.edu
Supercomputing  |||  UUCP:     {uunet,convex,pur-ee}!uiucuxc!uicsrd!mcdaniel
Research and    |||  ARPANET:  mcdaniel%uicsrd@uxc.cso.uiuc.edu
Development,    |||  CSNET:    mcdaniel%uicsrd@uiuc.csnet
U of Illinois   |||  DECnet:   GARCON::"mcdaniel@uicsrd.csrd.uiuc.edu"