From: Dan Cross <crossd@gmail.com>
To: Rich Salz <rich.salz@gmail.com>
Cc: segaloco <segaloco@protonmail.com>, COFF <coff@tuhs.org>
Subject: [TUHS] Re: Unix game origins - stories similar to Crowther's Adventure
Date: Wed, 1 Feb 2023 14:16:33 -0500 [thread overview]
Message-ID: <CAEoi9W54YtpeJYxO0tz39eDyk2U7jUchSFaqp1DAMgF7E_G2ug@mail.gmail.com> (raw)
In-Reply-To: <CAFH29tpp+kxcCTkFykuUW+dtcU=na8btAMmFCaLk=O8VA_GV-A@mail.gmail.com>
[TUHS to Bcc]
On Wed, Feb 1, 2023 at 2:11 PM Rich Salz <rich.salz@gmail.com> wrote:
> On Wed, Feb 1, 2023 at 1:33 PM segaloco via TUHS <tuhs@tuhs.org> wrote:
>> In the annals of UNIX gaming, have there ever been notable games that have operated as multiple processes, perhaps using formal IPC or even just pipes or shared files for communication between separate processes (games with networking notwithstanding)?
>
> https://www.unix.com/man-page/bsd/6/hunt/
> source at http://ftp.funet.fi/pub/unix/4.3bsd/reno/games/hunt/hunt/
Hunt was the one that I thought of immediately. We used to play that
on Suns and VAXen and it could be lively.
There were a number of such games, as Clem mentioned; others I
remember were xtrek, hearts, and various Chess and Go servers.
- Dan C.
next prev parent reply other threads:[~2023-02-01 19:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 2:30 [TUHS] " Will Senn
2023-02-01 2:58 ` [TUHS] " Clem Cole
2023-02-01 4:50 ` Douglas McIlroy
2023-02-01 5:36 ` Rob Pike
2023-02-01 20:23 ` Dave Horsfall
2023-02-02 15:35 ` Marc Donner
2023-02-03 2:15 ` Adam Thornton
2023-02-01 6:27 ` Jonathan Gray
2023-02-01 7:09 ` Jonathan Gray
2023-02-01 14:41 ` Rich Salz
2023-02-01 15:22 ` Will Senn
2023-02-01 17:34 ` Rich Salz
2023-02-01 17:52 ` Henry Bent
2023-02-01 18:33 ` segaloco via TUHS
2023-02-01 19:09 ` Rich Salz
2023-02-01 19:16 ` Dan Cross [this message]
2023-02-01 20:21 Douglas McIlroy
2023-02-01 20:41 ` A. P. Garcia
2023-02-01 20:47 ` ron minnich
2023-02-01 23:31 ` Douglas McIlroy
2023-02-01 23:24 ` Dan Cross
2023-02-02 0:43 Noel Chiappa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEoi9W54YtpeJYxO0tz39eDyk2U7jUchSFaqp1DAMgF7E_G2ug@mail.gmail.com \
--to=crossd@gmail.com \
--cc=coff@tuhs.org \
--cc=rich.salz@gmail.com \
--cc=segaloco@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).