Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!qns3.qns.com!imci4!newsfeed.internetmci.com!news.mathworks.com!fu-berlin.de!zib-berlin.de!irz401!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Is replacing /bin/sh with bash recommended? Date: 22 Mar 1996 00:29:26 GMT Organization: Private BSD site, Dresden Lines: 20 Message-ID: <4iss96$eor@uriah.heep.sax.de> References: <4ih5qb$lae@blackice.winternet.com> <4iq2s6$33o@electra.saaf.se> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.3 gorhas@electra.saaf.se (G|ran Hasse) writes: > >What sort of nasties (if any) should I expect if I replace /bin/sh > >with bash in FreeBSD-2.1.0? > > > > You should NOT!!! do this. Some system scripts might use /bin/sh or some > future programmer might use /bin/sh as the "old" shell. That's about as wrong as all the opposite opinions here: ash (/bin/sh) is an ``almost Posix'' shell, meaning you can do all the nifty things Posix is so proud of: $(cmd), $((expr)), aliases, $ENV, etc. Even command-line editing is there. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)