*BSD News Article 31951


Return to BSD News archive

Xref: sserve comp.os.386bsd.questions:11061 gnu.misc.discuss:15333
Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!gatech!nntp.msstate.edu!olivea!grapevine.lcs.mit.edu!usenet.coe.montana.edu!bsd.coe.montana.edu!nate
From: nate@bsd.coe.montana.edu (Nate Williams)
Newsgroups: comp.os.386bsd.questions,gnu.misc.discuss
Subject: Re: Taylor UUCP on FreeBSD???
Date: 21 Jun 1994 02:02:23 GMT
Organization: Montana State University, Bozeman  Montana
Lines: 38
Message-ID: <2u5hnf$svv@pdq.coe.montana.edu>
References: <1994Jun13.040754.17764@kosman.uucp> <2tv1s5$jnn@news.demos.su> <2u53jg$rrk@pdq.coe.montana.edu> <2u5bom$cb6@glitnir.ifi.uio.no>
NNTP-Posting-Host: 153.90.192.29

>++--- Max Klochkov:
>|| I solved this problem by linking /bin/sh to /usr/local/bin/bash
>||
>+--- Nate Williams:
>| This is in general 'A Bad Thing' to do. This really screws up the
>| default build tools, and will bite you if you try to build the world
>| with the BSD make tools.
>| 
>With all due respect, I suggest that you clean up your "default build
>tools" so that they work with bash instead of tying your users to a
>non-standard Bourne shell.

ash is more standard than bash, and is MUCH (!!!) smaller.  Why use a
swiss army knife when a pen-knife works just fine.  If you want to use
bash as your login shell, so be it, but I'll kick and scream when you
tell me that it has to be the shell used for programming and such.  I
don't need command line editing, history and the like for simple scripts
in the system.

>bash works fine as /bin/sh in Linux. The only problem I'm aware of is
>a bug in Cnews (redirecting before a sub-shell).

And there was a big push a while back to replace bash with ash due
to it's size.  Again, for an interactive shell bash is great, but
for system performance it just doesn't stack up.

For an example of this look through the archives and get the article
Kees Bot posted on fork/exec times on Linux, Minix, and the BSD's.  The
fork/exec time was almost directly related to the size of the /bin/sh
process.  (Even with shared memory and the like on Linux)


Nate
-- 
nate@bsd.coe.montana.edu     |  FreeBSD core member and all around tech.
nate@cs.montana.edu          |  weenie.
work #: (406) 994-4836       | 
home #: (406) 586-0579       |  Available for contract/otherwise work.