Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!agate!helios.ee.lbl.gov!epb2.lbl.gov!envbvs
From: envbvs@epb2.lbl.gov (Brian V. Smith)
Newsgroups: comp.sys.dec
Subject: Re: Need Info on DEC CPUs
Message-ID: <2788@helios.ee.lbl.gov>
Date: 7 Jun 89 16:52:11 GMT
References: <62866@yale-celray.yale.UUCP>
Sender: usenet@helios.ee.lbl.gov
Reply-To: bvsmith@lbl.gov
Organization: Lawrence Berkeley Laboratory
Lines: 28

> 
> There are two halves to DECwindows:  The client, which does the computing, and
> the server, which does the displaying.  Any VAX can run the client software
> (assuming it is running at least V5.1 of VMS).  A client has to be a worksta-
> tion;

This is most certainly NOT true. I have run X clients on Sun servers, Vax11/780s,
Vax8650 (running 4.3BSD), etc.  There is no requirement that the client run
on a workstation, or that it be running underVMS.  It just needs to have some
sort of connection to the server (TCP/IP or DECNET, for example.)

The DECwindows SERVER runs under Ultrix besides VMS.
In fact, version 1.0 of the Ultrix Windowing Software (UWS1.0), which is
equivalent to X version 10.3 (or .4?) only runs under Ultrix.

Now, the server must by definition run on a machine with a display.  This
is usually one of the criteria for a workstation computer; that it has a
graphic display of some sort.

One can usually mix and match clients and servers.   That is, you could run
an X client on a Sun and display its graphics on your local workstation of 
any flavor running (DECwindows or X from MIT, or any other X server).
That is merely one of the nice things about X.

_____________________________________
Brian V. Smith    (bvsmith@lbl.gov)
Lawrence Berkeley Laboratory
The usual disclaimers apply.