Date: Fri, 12 Nov 2004 09:50:05 -0800 From: Paul Armstrong <freebsdhackers@otoh.org> To: Avleen Vig <lists-freebsd@silverwraith.com>, Kevin Lyons <klyons@corserv.com>, freebsd-hackers@freebsd.org Subject: Re: tcsh fix Message-ID: <20041112175005.GG1807@suricate.otoh.org> In-Reply-To: <20041112160528.GA91711@falcon.midgard.homeip.net> References: <41940880.7070409@corserv.com> <20041112023023.GG19417@silverwraith.com> <20041112031122.GA87071@falcon.midgard.homeip.net> <20041112055543.GH19417@silverwraith.com> <20041112160528.GA91711@falcon.midgard.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 12, 2004 at 05:05:28PM +0100, Erik Trulsson wrote: > > This is to provide compatibility whn working with multiple versions of > > Unix. > > I write many scripts in sh on Solaris, and find they just don't work on > > Linux because /bin/sh on Linux is really /bin/bash and is not bacwards > > compatible. I HATE this. We shouldn't do this, and should do anything > > like this. > > Again - backwards compatible with what? Might it not be the case that > it is your scripts for Solaris-sh which uses non-standard features and > therefore fails on bash (which actually tends to be very > standards-compliant.) Indeed. Keep in mind that if you want a standard Bourne implementation on Solaris (or at least one that complies to POSIX.2a-1992), then you need to start your scripts with /usr/xpg4/bin/sh rather than /bin/sh. Given that it's easier (and shouldn't actually do any harm to the base OS) to commit the 44bsd csh as /bin/csh (or just simply remove the link for /bin/csh->/bin/tcsh) than continue to argue about this, would someone with a commit bit please make this thread go away? Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041112175005.GG1807>