Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA2166 ; Fri, 26 Feb 93 16:31:10 EST Xref: sserve comp.os.386bsd.development:34 comp.os.386bsd.bugs:19 Newsgroups: comp.os.386bsd.development,comp.os.386bsd.bugs Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!tandem!UB.com!quack!dfox From: dfox@quack.sac.ca.us (David Fox) Subject: Re: Is fixing /bin/sh worthwhile? Message-ID: <fZPePT0@quack.sac.ca.us> Organization: The Duck Pond public unix: +1 408 249 9630, log in as 'guest'. References: <CONKLIN.93Feb23174603@talisman.kaleida.com> Date: 25 Feb 1993 21:57:17 UTC Lines: 29 In article <CONKLIN.93Feb23174603@talisman.kaleida.com> conklin@kaleida.com writes: >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. This might be a good idea, except that bash takes up a good deal more memory than does sh. This could lead to problems on machines without lots of RAM. >replaced by bash, zsh, pd-ksh, or whatever in a future release. I've got the new zsh which was posted in comp.sources.misc recently compiled and running. It's a pretty nice shell, but takes almost as much RAM as bash does. >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 -- ------------------------------------------------------------------------ in real life: david fox email: dfox@quack.sac.ca.us 5479 Castle Manor Drive, San Jose, CA 95129 "Thanks for letting me change some USA magnetic patterns on your HD" -me 408-253-7992 "You've just won an absolutely FREE trip to the Isles of Langerhans" -me ------------------------------------------------------------------------