The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Doug McIlroy <doug@cs.dartmouth.edu>, TUHS <tuhs@tuhs.org>
Subject: [TUHS] Unix "Multiplexed Files"
Date: Wed, 8 Feb 2023 17:39:39 -0500	[thread overview]
Message-ID: <CAEoi9W69V2yBVAtOi9eVQ95bo2toUuta1gj1q77rssg8zu0huA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]

The subject of Communication Files on DTSS came up recently, and Doug
linked to this wonderful note:
https://www.cs.dartmouth.edu/~doug/DTSS/commfiles.pdf

Over on the Multicians list, I raised a question about the history of the
DTSS emulator on Multics in response to that, which sadly broke down into
antagonism, the details of which aren't terribly interesting. But Barry
Margolin suggested that the closest modern Unix analogue of Communication
Files were pseudo-TTYs, that had generated a dustup here. Doug's note
suggests that Plan 9's userspace filesystems, aided and abetted by mutable
namespaces and 9P as a common sharing mechanism, were a closer analogy.

But I wonder if multiplexed files were perhaps an earlier analogue; my
cursory examination of mpx(2) shows some similarities to the description of
the DTSS mechanism.

But I confess that I know very little about these, other than that they
seem to be an evolutionary dead end (they don't survive in any modern Unix
that I'm aware of, at any rate). I don't see much about them in my
archives; Paul Ruizendaal mentioned them tangentially in 2020 in relation
to non-blocking IO: they are, apparently, due to Chessen?

Does anyone have the story here?

        - Dan C.

[-- Attachment #2: Type: text/html, Size: 1487 bytes --]

             reply	other threads:[~2023-02-08 22:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 22:39 Dan Cross [this message]
2023-02-08 23:40 ` [TUHS] " Rob Pike
2023-02-08 23:52 ` Eric Allman

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=CAEoi9W69V2yBVAtOi9eVQ95bo2toUuta1gj1q77rssg8zu0huA@mail.gmail.com \
    --to=crossd@gmail.com \
    --cc=doug@cs.dartmouth.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).