Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ucla-cs!zen!ucbvax!jade!violet.berkeley.edu!jkh
From: jkh@violet.berkeley.edu (Jordan K. Hubbard)
Newsgroups: comp.arch
Subject: WANTED: Unified operating system for Sun/uVax II & 2000
Message-ID: <4646@jade.BERKELEY.EDU>
Date: Sat, 8-Aug-87 17:57:12 EDT
Article-I.D.: jade.4646
Posted: Sat Aug  8 17:57:12 1987
Date-Received: Sun, 9-Aug-87 20:43:03 EDT
Sender: usenet@jade.BERKELEY.EDU
Reply-To: jkh@violet.berkeley.edu (Jordan K. Hubbard)
Organization: University of California, Berkeley
Lines: 29

I've got a Vaxstation II, a Vaxstation 2000 and a Sun 3/50 (w/ tape and 86MB
disk) forming a small cluster. The II and the 2000 both have monochrome qvss
displays (actually, I suppose it's not right to call the display on the 2000
a qvss display, since it has no Q-bus but it *acts* like a qvss. so...).

The 3/50 has its standard Sun display..
They all, of course, run X..

Here's the question.. The uVaxen run Ultrix 2.0, the sun runs 3.3.. This is
fine and dandy, but what I'd *really* like is to run *ONE* OS for all
three.. It's probably way too much to ask, but it seems kind of a pain
to have to support 2 different man page trees, have things occasionally
break when porting etc.. I use NFS *alot*. It's become almost mandatory
at this point because of limited disk resources on each machine, so that's
got to be supported.. Natually, uVaxen and 3/50's are not blindingly fast and I
don't have much memory (3MB on the II, 6MB on the 2000 and 4MB on the Sun),
so I need something that's as efficient and compact as possible.

With all these considerations in mind, would Mach be a good idea? How
about this "wisconsin" 4.3 I've seen mentioned? Would they support the
graphics displays and NFS? Would X (version 10) compile with the existing
qvss and Sun ddx libraries?

I probably want far too much.. I guess I'll be stuck with Ultrix and 
Sun 3.x.. 

					Jordan Hubbard
					U.C. Berkeley
					jkh@violet.berkeley.edu