From: Dan Cross <firstname.lastname@example.org>
To: Douglas McIlroy <email@example.com>
Cc: COFF <firstname.lastname@example.org>
Subject: [COFF] Re: [TUHS] Re: Unix game origins - stories similar to Crowther's Adventure
Date: Wed, 1 Feb 2023 18:24:18 -0500 [thread overview]
Message-ID: <CAEoi9W48Xn5hgGqdVQdRv7JWY4poosrW46_akBOSc8W8ksENdg@mail.gmail.com> (raw)
[TUHS to Bcc]
On Wed, Feb 1, 2023 at 3:23 PM Douglas McIlroy
> > 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
> I don't know any Unix examples, but DTSS (Dartmouth Time Sharing
> System) "communication files" were used for the purpose. For a fuller
> story see https://www.cs.dartmouth.edu/~doug/DTSS/commfiles.pdf
Interesting. This is now being discussed on the Multicians list (which
had a DTSS emulator! Done for use by SIPB). Warren Montgomery
discussed communication files under DTSS for precisely this kind of
thing; apparently he had a chess program he may have run under them.
Barry Margolin responded that he wrote a multiuser chat program using
them on the DTSS system at Grumman.
Margolin suggests a modern Unix-ish analogue may be pseudo-ttys, which
came up here earlier (I responded pointing to your wonderful note
> > This is probably a bit more Plan 9-ish than UNIX-ish
> So it was with communication files, which allowed IO system calls to
> be handled in userland. Unfortunately, communication files were
> complicated and turned out to be an evolutionary dead end. They had
> had no ancestral connection to successors like pipes and Plan 9.
> Equally unfortunately, 9P, the very foundation of Plan 9, seems to
> have met the same fate.
I wonder if there was an analogy to multiplexed files, which I admit
to knowing very little about. A cursory glance at mpx(2) on 7th
Edition at least suggests some surface similarities.
- Dan C.
next parent reply other threads:[~2023-02-01 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKH6PiU1aLmUq585mBMmMmZfpuwSAE3sx-UQoj=dn5-pb-w5DA@mail.gmail.com>
2023-02-01 23:24 ` Dan Cross [this message]
[not found] <email@example.com>
[not found] ` <CAEdTPBertjtWMaCA5gDbUDjPMgvHwdqHbsxJ9dnw6t2oSWxnWA@mail.gmail.com>
[not found] ` <9rlsK1lcp2ffNj2lkBadLwVDPzGlSjgLbwwByJXMv4FDhSsmezMSUlcXw4jZjc0rM8XtULgrAv6I2g-nurUzaS_fZicDHORQVLSU0fzEydYfirstname.lastname@example.org>
2023-02-01 19:02 ` Clem Cole
[not found] ` <CAFH29tpp+kxcCTkFykuUW+dtcU=na8btAMmFCaLk=O8VA_GV-A@mail.gmail.com>
2023-02-01 19:16 ` Dan Cross
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).