Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!sdd.hp.com!uakari.primate.wisc.edu!pikes!mercury.cair.du.edu!diana.cair.du.edu!rwelch From: rwelch@diana.cair.du.edu (RANDY S WELCH) Newsgroups: comp.unix.shell Subject: Re: Questions concerning BaSH Message-ID: <1991Jan10.062645.17718@mercury.cair.du.edu> Date: 10 Jan 91 06:26:45 GMT References: <71792@bu.edu.bu.edu> Sender: news@mercury.cair.du.edu (netnews) Organization: University of Denver Lines: 34 In-Reply-To: melling@cs.psu.edu's message of 9 Jan 91 21:37:26 GMT In article melling@cs.psu.edu (Michael D Mellinger) writes: Path: mercury.cair.du.edu!pikes!csn!ncar!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!news From: melling@cs.psu.edu (Michael D Mellinger) Newsgroups: comp.unix.shell Date: 9 Jan 91 21:37:26 GMT References: <71792@bu.edu.bu.edu> Sender: news@cs.psu.edu (Usenet) Organization: Penn State Computer Science Lines: 9 Nntp-Posting-Host: client6.cs.psu.edu I found BASH 1.05 to be very unstable. I wouldn't use it as my login shell. There are several major patches for it that you should be sure to get if you decide to use it. I might try it again when 1.06 is released. For now though, I recommend tcsh. -Mike BTW: The BASH binary(like most GNU binaries) is quite large. There are several of us in my office that use bash as a login shell. True you need to apply patches ( history/Sys V signal handling ), but it works well for us. If you need to cut down the size, get rid of the help documentation (40K). It has to execute scripts somewhat better than our brain damaged csh... -randy -- Randy Welch Mail to : ...!ncar!scicom!bldr!randy or rwelch@du.edu Boulder, CO VOICE : 303-442-6717 "Unfortunately, life contains an unavoidable element of unpredictability" -David Lynch "The Angriest Dog in the World"