Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.telstra.net!act.news.telstra.net!imci3!imci4!newsfeed.internetmci.com!news.kei.com!nntp.coast.net!harbinger.cc.monash.edu.au!ns.saard.net!news.camtech.com.au!calypso.bns.com.au!not-for-mail From: mike@calypso.bns.com.au (Michael Talbot-Wilson) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Is replacing /bin/sh with bash recommended? Date: 23 Mar 1996 23:49:33 +1030 Organization: Calypso & That Jazz Lines: 11 Message-ID: <4j0tp5$shj@calypso.bns.com.au> References: <4ih5qb$lae@blackice.winternet.com> <4ipkqm$t6h@adv.IAEhv.nl> NNTP-Posting-Host: calypso.bns.com.au X-Newsreader: NN version 6.5.0 CURRENT #3 devet@adv.IAEhv.nl (Arjan de Vet) writes: >At least on 2.0.5 I still had to use bash 1.14 to run some shell scripts >from INN 1.4: /bin/sh would give very strange errors, even infinite loops >if I remember correctly. Earlier /bin/sh versions were much worse breaking >even more scripts (Pnews from trn), so I just replaced /bin/sh with bash >on older FreeBSD versions. You remind me that I had similar problems compiling INN and strn. Perhaps because they weren't official FreeBSD "ports". Yes, they were fixed by switching to bash.