The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Eric Allman <tuhs@eric.allman.name>
To: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Unix "Multiplexed Files"
Date: Wed, 8 Feb 2023 15:52:34 -0800	[thread overview]
Message-ID: <217e7cf8-cc0e-ffb4-efb8-d7ea6edf5b4d@neophilic.com> (raw)
In-Reply-To: <CAEoi9W69V2yBVAtOi9eVQ95bo2toUuta1gj1q77rssg8zu0huA@mail.gmail.com>

As it turns out, the first implementation of syslog used mpx files,
albeit arguably abusing them. I don't remember the details. mpx files
have long since been replaced by modern alternatives.

eric


On 2023-02-08 14:39 , Dan Cross wrote:
> 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.
>

      parent reply	other threads:[~2023-02-10  1:30 UTC|newest]

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

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=217e7cf8-cc0e-ffb4-efb8-d7ea6edf5b4d@neophilic.com \
    --to=tuhs@eric.allman.name \
    --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).