Article View: comp.bugs.sys5
Article #633Re: sh bug
From: guy
Date: Thu, 29 Oct 1987 01:23
Date: Thu, 29 Oct 1987 01:23
11 lines
1061 bytes
1061 bytes
> 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.
I tried "/bin/sh" on a 3B2 running S5R3.1. The "echo" command is not run.
Thus, the bug must have been fixed in your version, since no version AT&T puts
out as part of their porting base has it fixed.
Guy Harris
{ihnp4, decvax, seismo, decwrl, ...}!sun!guy
guy@sun.com
Technical Details
Message-ID:
<32303@sun.uucp>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!rutgers!husc6!hao!ames!amdahl!oliveb!sun!gorodish!guyReferences:
<467@virginia.acc.virginia.edu> <7719@steinmetz.steinmetz.UUCP>Show Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!rutgers!husc6!hao!ames!amdahl!oliveb!sun!gorodish!guy From: guy@gorodish.UUCP Newsgroups: comp.bugs.sys5 Subject: Re: sh bug Message-ID: <32303@sun.uucp> Date: Wed, 28-Oct-87 20:23:05 EST Article-I.D.: sun.32303 Posted: Wed Oct 28 20:23:05 1987 Date-Received: Sun, 1-Nov-87 02:59:18 EST References: <467@virginia.acc.virginia.edu> <7719@steinmetz.steinmetz.UUCP> Sender: news@sun.uucp Lines: 11