The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [TUHS] Re: Unix game origins - stories similar to Crowther's Adventure
Date: Wed,  1 Feb 2023 19:43:28 -0500 (EST)	[thread overview]
Message-ID: <20230202004328.8872918C073@mercury.lcs.mit.edu> (raw)

    > segaloco 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)?

The machine of the DSSR/RTS group at MIT-LCS, Steve Ward's group (an -11/70
running roughly PWB1) had an implementation of a form of Perquackey:

  https://en.wikipedia.org/wiki/Perquackey

that was a multi-player game; I'm pretty sure there was a process per player,
and they communicated, I'm pretty sure, through pipes, not files - there was
certainly no IPC in that system.

IIIRC, the way it worked was that there was a parent process, and it spawned
a child process for each terminal that was playing, and the children could
all communicate through pipes. (They had to communicate because in that
version, all the players shared a single set of dice, and once one person had
played a word, the other players couldn't play that word. So speed was
important in playing; people got really addicted to it.)

Alas, although their machine was very similar to CSR's (although ours was an
-11/45 with an Able ENABLE and a lot of memory, making it a lot more like a
/70), and we shared most code between the machines, and I have a full dump of
the CSR machine, we apparently didn't have any of the games on the CSR
machine, so I can't look at the source to confirm exactly how it worked.

        Noel

             reply	other threads:[~2023-02-02  0:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02  0:43 Noel Chiappa [this message]
  -- strict thread matches above, loose matches on Subject: below --
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-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

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=20230202004328.8872918C073@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    --cc=tuhs@tuhs.org \
    /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).