From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 15 15:30:28 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2089916A4CE for ; Mon, 15 Nov 2004 15:30:28 +0000 (GMT) Received: from smradoch.ath.cx (r2g224.chello.upc.cz [62.245.70.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECD9C43D3F for ; Mon, 15 Nov 2004 15:30:26 +0000 (GMT) (envelope-from neuhauser@chello.cz) Received: by smradoch.ath.cx (Postfix, from userid 1001) id EA6E11F87BED; Mon, 15 Nov 2004 16:30:24 +0100 (CET) Date: Mon, 15 Nov 2004 16:30:24 +0100 From: Roman Neuhauser To: Avleen Vig , Kevin Lyons , freebsd-hackers@freebsd.org Message-ID: <20041115153024.GA2846@isis.wad.cz> Mail-Followup-To: Avleen Vig , Kevin Lyons , freebsd-hackers@freebsd.org References: <41940880.7070409@corserv.com> <20041112023023.GG19417@silverwraith.com> <20041112031122.GA87071@falcon.midgard.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041112031122.GA87071@falcon.midgard.homeip.net> User-Agent: Mutt/1.5.6i Subject: Re: tcsh fix X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 15:30:28 -0000 # ertr1013@student.uu.se / 2004-11-12 04:11:22 +0100: > The only real problem with having bash as /bin/sh is that people tend > to write scripts using bash-specific features and forget that such > scripts are not portable to systems using a less powerful /bin/sh. Or the other way around. Bash (at least the one from RHEL 3.0) is seriously broken, these two things are more than it can handle (as opposed to our /bin/sh): $(case $foo in x) do_x;; y) do_y;; esac) out=`mktemp ...` $otherscript >$out 2&1 where $otherscript contains $(x | tee /dev/stderr | y) I stumbled upon these when I was porting periodic(8) to RHEL. So, my description would be that people run into problems when they write scripts using sh-specific features and forget that such scripts are not portable to systems using a less powerful bash. ;) -- If you cc me or remove the list(s) completely I'll most likely ignore your message. see http://www.eyrie.org./~eagle/faqs/questions.html