Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!viking.UUCP!dpb
From: dpb@viking.UUCP
Newsgroups: comp.windows.x
Subject: Re: xtrek problem
Message-ID: <8810200505.AA16306@viking.frame.com>
Date: 20 Oct 88 05:05:11 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 13


> Everybody playing in the same game must start a process on the same machine--
> i.e., the xtrek daemon runs on only one machine:  everyone forks a remote shell
> on the xtrek "server."  e.g.,
> 	rsh <hostmachine> /users/usr/games/xtrek $DISPLAY & 
> The usual procedure is to use the fastest machine around as the xtrek server.

Even better, some guys at HP in Palo Alto had an xtrek jump starter 
configured so you did:

   telnet <hostname> 1701

It would prompt you for you for a display name, and send an xtrek your way.