Date: Wed, 04 May 2005 19:27:25 -0600 From: Scott Long <scottl@samsco.org> To: Charles Swiger <cswiger@mac.com> Cc: Warner Losh <imp@bsdimp.com> Subject: Re: boot banner project Message-ID: <4279767D.5010203@samsco.org> In-Reply-To: <ff3ef3b2621f16316effcf296f044d93@mac.com> References: <20050504113817.GD22956@empiric.icir.org> <20050504132429.GA2105@uk.tiscali.com> <5207b55e44478fa93e3689ad79b54f4d@mac.com> <20050504.152439.71089989.imp@bsdimp.com> <ff3ef3b2621f16316effcf296f044d93@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Charles Swiger wrote: > On May 4, 2005, at 5:24 PM, Warner Losh wrote: > >>> Agreed. I consider it a serious misfortune that FreeBSD doesn't use >>> /bin/sh as root's shell. On the other hand, it's easy enough to fix, >>> so I haven't spent my time complaining about this. :-) >> >> >> All BSDs have, since a very long time ago, used /bin/csh as root's >> shell. > > > NEXTSTEP never did; and neither does OS X: > OSX used csh by default until the 10.3 series release. You can still (thankfully) select it. IMHO, csh/tcsh is superior for interactive use, and bash/ksh is superior for scripting. It's amazing what happens when you pick the right tool for the job; hammers are vastly superior at pounding nails, while screw drivers are vastly superior at turning screws. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4279767D.5010203>