Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!homxb!whuts!mtune!codas!usfvax2!chips
From: chips@usfvax2.UUCP
Newsgroups: comp.arch,comp.unix.wizards
Subject: Re: Free Software Foundation (was: Re: Mach, the new standard?)
Message-ID: <846@usfvax2.UUCP>
Date: Wed, 30-Sep-87 09:12:50 EDT
Article-I.D.: usfvax2.846
Posted: Wed Sep 30 09:12:50 1987
Date-Received: Sun, 4-Oct-87 01:08:23 EDT
References: <8490@think.UUCP> <1745@ncr-sd.SanDiego.NCR.COM> <819@sugar.UUCP> <15124@topaz.rutgers.edu>
Organization: AT Engineering, Tampa, FL
Lines: 21
Xref: utgpu comp.arch:2312 comp.unix.wizards:4309
Summary: Bourne shell brain damage

In article <15124@topaz.rutgers.edu>, Ron Natalie writes:
> In addition, the shell does user mode page faults
> to know when to grow its heap.
> 
> -Ron

Don't I know it!  I tried to port the Bourne shell (v7) to a 68000 box running
UNOS, which was Charles River Data System's answer to UNIX.  UNOS was no
problem, but since the 68000 doesn't know how to restart instructions that
cause bus faults, I *never* got sh to work reliably.  (People used it anyway,
which shows you how bad CRDS's command interpreter was!)

The C shell, on the other hand, worked right out of the box.  (Thanks, Bill!)
Of course, I had to adapt for UNOS job control -- wait() could return the same
pid any number of times as processes were suspended and restarted -- but that's
peanuts in the porting game.  :-)

-- 
Chip Salzenberg            "chip%ateng.uucp@UU.NET"  or  "uunet!ateng!chip"
A.T. Engineering, Tampa    CIS: 73717,366    Last Chance: "chips@usfvax2.UUCP"
"Use the Source, Luke!"    My opinions do not necessarily agree with anything.