Path: utzoo!attcan!uunet!husc6!bbn!rochester!pt.cs.cmu.edu!ius3.ius.cs.cmu.edu!ralphw
From: ralphw@ius3.ius.cs.cmu.edu (Ralph Hyre)
Newsgroups: comp.arch
Subject: Re: What's a "tahoe"?
Message-ID: <2642@pt.cs.cmu.edu>
Date: 8 Aug 88 21:37:00 GMT
References: <6341@bloom-beacon.MIT.EDU> <60859@sun.uucp> <474@m3.mfci.UUCP> <2620@pt.cs.cmu.edu> <12889@mimsy.UUCP>
Sender: netnews@pt.cs.cmu.edu
Organization: Carnegie-Mellon University, CS/RI
Lines: 19

In article <12889@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
[about 4.3-tahoe]
>It is also nice to have two differing architectures around in order
>to test portability: the new VM will be able to run on a virtual-
>address-cache architecture right away, since the Tahoe is such a machine.
>(Incidentally, tweaking the old VAX-oriented code to work on that machine
>took surprisingly few changes.)
One might wonder why they didn't go with Suns, since they have a friend in 
a high place (Bill Joy), and could also presumably get good deals on them :-)
I heard that Sun runs SunOS on Vaxen for internal testing purposes, it would
be interesting if Berkeley sported 4.3 on Suns, since it would fix even more
portability problems like NULL derefs and such.

I can see that advantage in not breaking everything at once, however :-)
-- 
					- Ralph W. Hyre, Jr.

Internet: ralphw@ius2.cs.cmu.edu    Phone:(412)268-{2847,3275} CMU-{BUGS,DARK}
Amateur Packet Radio: N3FGW@W2XO, or c/o W3VC, CMU Radio Club, Pittsburgh, PA