Date: Fri, 16 Aug 2002 23:06:06 +0200 From: Erik Trulsson <ertr1013@student.uu.se> To: "David O'Brien" <obrien@FreeBSD.org> Cc: Anders Nordby <anders@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/audio/opennap/files opennap.sh ports/databases/msql/files msql2.sh ports/emulators/vmware-guestd/files vmware-guestd.sh ports/games/fsgs/files fsgs.sh ports/games/uox3/files uox3.sh ports/net/rtsp_proxy/files rtsp_proxy.sh ports/net/rwhois/files ... Message-ID: <20020816210605.GB8593@falcon.midgard.homeip.net> In-Reply-To: <20020816200824.GC22129@dragon.nuxi.com> References: <200208140014.g7E0E8Z4019514@freefall.freebsd.org> <20020816200824.GC22129@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 16, 2002 at 01:08:24PM -0700, David O'Brien wrote:
> On Tue, Aug 13, 2002 at 05:14:07PM -0700, Anders Nordby wrote:
> > Log:
> > Fix startup-scripts for -current /bin/sh issues.
>
> Why did things like:
>
> [ -x ${PREFIX}/sbin/opennap ] && ${PREFIX}/sbin/opennap > /dev/null 2>& 1 & && echo -n ' opennap'
>
> stop working?
Because constructions of the type
cmd1 & && cmd2
are no longer accepted as valid syntax by /bin/sh.
(Actually, what isn't accepted any longer is '&&' or '||' as the first
token of a command.)
The fact that it was accepted before was a bug in /bin/sh.
(In case you wonder, bash, pdksh, zsh and Solaris /bin/sh don't accept
it either, so it wasn't a portable construction anyway.)
--
<Insert your favourite quote here.>
Erik Trulsson
ertr1013@student.uu.se
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020816210605.GB8593>