Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!caip!meccts!dicome!mn-at1!alan
From: alan@mn-at1.UUCP (Alan Klietz)
Newsgroups: net.unix
Subject: Re: XWINDOWS question
Message-ID: <144@mn-at1.UUCP>
Date: Wed, 27-Aug-86 12:40:56 EDT
Article-I.D.: mn-at1.144
Posted: Wed Aug 27 12:40:56 1986
Date-Received: Thu, 28-Aug-86 22:36:07 EDT
References: <465@houxv.UUCP> <6514@sun.uucp>
Lines: 30
Summary: Porting to System V is easy if you have TCP/IP

In article <6514@sun.uucp>, guy@sun.uucp (Guy Harris) writes:
> > Can it run under UNIX 5.2 or greater?
> 
> Not without some work.  It may use the new reliable signal mechanism from
> 4.2BSD.  It is a server-based window system; programs running under X do not
> directly paint bits on the screen, they send messages to the X server and it
> paints the bits.  Furthermore, it does not directly read events from
> keyboards or mice either; the server reads them and sends messages to
> clients.  As such, it requires a bidirectional interprocess communication
> mechanism of some sort; it currently uses UNIX-domain sockets and
> Internet-domain sockets.
> 

I ported client X Windows to a CRAY-2 running Unicos (a System V variant)
without much problem.   You do need some kind of reliable transport protocol.

(I used Wollogong's TCP/IP implementation, which follows the 4.2bsd socket
protocols close enough that I ported the socket code pretty much unchanged.)
--
Alan Klietz
Minnesota Supercomputer Center (*)
1200 Washington Avenue South
Minneapolis, MN  55415    UUCP:  ..ihnp4!dicome!mn-at1!alan (unreliable)
Ph: +1 612 638 0577              ..caip!meccts!dicome!mn-at1!alan
                          ARPA:  aek@umn-rei-uc.ARPA

(*) An affiliate of the University of Minnesota

[Warning: umn-rei-uc is down until September 11th.   dicome will no
longer feed mail after Aug 29th.  Good luck..]