Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sunybcs!bingvaxu!leah!itsgw!steinmetz!davidsen
From: davidsen@steinmetz.UUCP
Newsgroups: comp.bugs.sys5
Subject: Re: sh bug
Message-ID: <7719@steinmetz.steinmetz.UUCP>
Date: Wed, 28-Oct-87 12:40:00 EST
Article-I.D.: steinmet.7719
Posted: Wed Oct 28 12:40:00 1987
Date-Received: Sat, 31-Oct-87 11:07:43 EST
References: <467@virginia.acc.virginia.edu>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: General Electric CRD, Schenectady, NY
Lines: 17

In article <467@virginia.acc.virginia.edu> mer6g@virginia.UUCP (Marc Rouleau) writes:
|On our 3b2, 3b5, and 3b15 AT&T systems running SYSV.2 and SYSV.3, sh does
|something rather unfortunate when certain built-in functions fail.  For
|example,
|
|	cd nowhere || echo 'cd failure'

Not all shells have this problem. I tried the Korn shell, "shV" sys V
shell in Xenix, and /bin/sh in a unix-pc. All return bad status when cd
fails. With the exception of ksh, there is no way to determine if the
bug has been fixed in my versions, or your is broken.

Hopefully someone can shed additional light on this.
-- 
	bill davidsen		(wedu@ge-crd.arpa)
  {uunet | philabs | seismo}!steinmetz!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me