Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!caip!princeton!allegra!ulysses!ucbvax!sdcsvax!hutch
From: hutch@sdcsvax.UUCP (Jim Hutchison)
Newsgroups: net.unix-wizards
Subject: Re: Pyramid system design
Message-ID: <1958@sdcsvax.UUCP>
Date: Wed, 30-Jul-86 02:16:53 EDT
Article-I.D.: sdcsvax.1958
Posted: Wed Jul 30 02:16:53 1986
Date-Received: Thu, 31-Jul-86 02:03:22 EDT
References: <1759@brl-smoke.ARPA> <976@decuac.DEC.COM> <459@oracle.UUCP> <5431@topaz.RUTGERS.EDU> <5561@sun.uucp> <5446@topaz.RUTGERS.EDU>
Reply-To: hutch@sdcsvax.UUCP (Jim Hutchison)
Organization: UCSD EMU Project (Educational Microcomputer Unix)
Lines: 18

In article <5446@topaz.RUTGERS.EDU> hedrick@topaz.RUTGERS.EDU (Charles Hedrick) writes:
>I don't know the exact reason for doing all of this, but I can guess.

Yet another consideration is the fact that you can write code that is portable
between the two "universes" and test this fact immediately, without 2 machines.
You can also do (pardon sudden relegious urge :-) work in the universe you
prefer for the vile universe (the one you may feel some disdain for).  Being
spoiled by unclean but useful job control and such does not make me not want
to use things like streams and shared memory.

Yes, I realize pyramids don't have streams, but its the concept!  Working in an
environment different from your test environment and being on the same machine.
Like sitting on a sun doing ms-dos work via cross-compiler, but without
having to change machines (or even have 2 machines).
-- 
    Jim Hutchison   UUCP:	{dcdwest,ucbvax}!sdcsvax!hutch
		    ARPA:	Hutch@sdcsvax.ucsd.edu
 "When you are going to die, a wombat is better than no company at all." -RZ