Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!wuarchive!udel!rochester!pt.cs.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!rh2y+
From: rh2y+@andrew.cmu.edu (Russell E. Hoffman, II)
Newsgroups: comp.os.os9
Subject: TOP bourne shell bugs?
Message-ID: <Ac07Qya00VADQ3ZVRM@andrew.cmu.edu>
Date: 8 Apr 91 13:59:26 GMT
Organization: Carnegie Mellon, Pittsburgh, PA
Lines: 20

Has anyone else incurred any particular bugs with the bourne-shell (sh)
that came with the TOP package? I have had a number of problems from time
to time that causes it to crash in a rather horrendous way, solvable only
by a reboot. The problem occurs when:

1.) I fire up sh
2.) I then run umacs
3.) From umacs I try to fork a shell
4.) I quit that shell
5.) Exit umacs
6.) Kablooey!

This generally results in a error 000:102 after every subsequent command I
type. Just wondering if anyone else has this problem.


cheers,
Russell Hoffman
rh2y+@andrew.cmu.edu
Carnegie Mellon University