Date: Wed, 04 May 2005 18:51:53 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: cswiger@mac.com Cc: freebsd-current@freebsd.org Subject: Re: boot banner project Message-ID: <20050504.185153.78707420.imp@bsdimp.com> In-Reply-To: <ddbd692bcfcae94e8417a228a95fbcfc@mac.com> References: <ff3ef3b2621f16316effcf296f044d93@mac.com> <20050504.163618.112621888.imp@bsdimp.com> <ddbd692bcfcae94e8417a228a95fbcfc@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <ddbd692bcfcae94e8417a228a95fbcfc@mac.com>
Charles Swiger <cswiger@mac.com> writes:
: I infer that POSIX compliance is not very important to you.
I have POSIX_ME_HARDER defined in my environement :-)
POSIX compliance for POSIX compliance sake isn't a goal.
: > I'm not looking for a catalog of systems. I'm telling you why
: > we are where we are today, and why things haven't changed: There's
: > really no need and inertial keeps things BSDish. Most people never
: > use the root shell directly, and all shell scripts are /bin/sh
: > anyway...
:
: The fact that the /etc/rc scripts, cron, and similar tools involving
: root's environment are all run using /bin/sh is one of the primary
: reasons why root shell ought to be /bin/sh. There are newgroup FAQs
: for various platforms which recommend against changing root's shell
: from being a /bin/sh.
That doesn't follow. All my shell scripts run /bin/sh, yet my default
shell is /bin/tcsh.
But like I've said twice now: There's lots of bigger problems in the
tree, and a change like this could break things. There's enough
breakage in the tree now.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050504.185153.78707420.imp>