Date: Sat, 15 Nov 2008 18:32:39 -0800 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: freebsd-questions@freebsd.org Subject: Re: root /etc/csh Message-ID: <20081116023239.GA89267@icarus.home.lan> In-Reply-To: <20081115061957.GA10998@ourbrains.org> References: <20081110110805.GK1302@obspm.fr> <20081110161002.GA81960@gizmo.acns.msu.edu> <20081110203643.GH27646@obspm.fr> <200811102235.46971.fbsd.questions@rachie.is-a-geek.net> <Pine.GSO.4.63.0811102239200.846@hmacs.cmi.ua.ac.be> <4ad871310811101530p7b2baa0fk7f7b5118e314c11d@mail.gmail.com> <4918CE42.3050504@ccstores.com> <20081115061957.GA10998@ourbrains.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 15, 2008 at 01:19:57AM -0500, dan-freebsd-questions@ourbrains.org wrote: > > isn't the "main reason" because other shells may reside on a filesystem > > which isn't necessarily mounted in maintenance/single user mode? Or, libraries > > for the same? > > -- > > Jim Pazarena fquest@ccstores.com > > Just link the shell of your choice statically and put it somewhere in /. > Problem solved. Why doesn't FreeBSD ship bash and other shells besides > the `sh' linked statically is beyond me. It wouldn't break ports, would > it? It does break ports. Very, very badly. I know because I've personally attempted replacing /bin/sh with bash as a "I have a weekend to spare" project. The topic of bringing bash into BSD as /bin/sh has been discussed in the past many, many times. It's always a heated discussion. We went through the same thing discussing bringing tcsh in (remember, /bin/csh is tcsh). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081116023239.GA89267>