The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Ruizendaal <pnr@planet.nl>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Any Good dmr Anecdotes?
Date: Mon, 2 Jul 2018 21:55:13 +0200	[thread overview]
Message-ID: <FC992FEB-FF0F-48DD-A7BC-2F41C3B98B88@planet.nl> (raw)


Not quite a dmr anecdote, but maybe this list can clear up a statement that dmr reputedly made: “streams means something different when shouted”.
I think the claim goes back to around the turn of the millennium and as far as I know it is not disputed that dmr either said this or could have said this.

Now, from reading this list over the years my understanding of the above statement is that dmr designed streams as a mechanism to clean up the kernel handling of line disciplines in a context of access via a terminal and/or modem, and that STREAMS developed this into a way to integrate network stacks with the kernel — hence streams meant something different when shouted.

The original dmr paper (1984) on streams (http://cm.bell-labs.co/who/dmr/st.html) seemed to support this understanding, focussing on terminal handling in its discussion. Also, near the end it says: "Streams are linear connections; by themselves, they support no notion of multiplexing, fan-in or fan-out. [...] It seems likely that a general multiplexing mechanism could help in both cases, but again, I do not yet know how to design it.” This seemed to exclude usage for networking, which is typically multiplexed.

However, now that the V8 sources are available it is clear that the streams mechanism was used (by dmr?) to implement TCP/IP networking. He explains how that tallies with the above quote on multiplexing in a 1985 usenet post: https://groups.google.com/forum/#!topicsearchin/net.unix-wizards/subject$3Astreams/net.unix-wizards/b7W_j_0qASU
(if the post by dmr does not immediately appear, click on the 8-10-85 post by 'd...@dutoit.uucp’ to make it fold out: this is the message I refer to).

The way I read this usenet post, dmr was actually reasonably content with implementing a network stack on top of (lowercase) streams. This then implies that he was alluding to something else when saying “streams means something different when shouted” (or maybe he never said it).

Any opinions on what he might have meant?








             reply	other threads:[~2018-07-02 19:55 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02 19:55 Paul Ruizendaal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-07-18  9:42 Hendrik Jan Thomassen
2018-07-03  7:27 arnold
2018-07-01 16:35 Norman Wilson
2018-06-30  1:31 Larry McVoy
2018-06-30  1:45 ` Jon Forrest
2018-06-30 18:43   ` Steve Johnson
2018-06-29  7:53 Warren Toomey
2018-06-29 10:53 ` ches@Cheswick.com
2018-06-29 12:51   ` John P. Linderman
2018-06-30  0:50   ` Steve Johnson
2018-06-30 11:44     ` Arrigo Triulzi
2018-06-30 22:42       ` Arthur Krewat
2018-06-30 23:29         ` Arrigo Triulzi
2018-07-01  4:17           ` Larry McVoy
2018-07-01 11:42           ` ron
2018-07-01  5:29       ` Dave Horsfall
2018-07-01  8:28         ` Arrigo Triulzi
2018-07-01 11:34         ` ron
2018-07-09 16:30           ` Random832
2018-07-09 17:13             ` Clem Cole
2018-07-10  5:54               ` arnold
2018-07-10  6:09                 ` George Michaelson
2018-07-10  7:19                   ` arnold
2018-07-11  0:20                     ` Noel Hunt
2018-07-11  1:31                       ` Larry McVoy
2018-07-11  1:37                         ` George Michaelson
2018-07-11  1:37                         ` ron minnich
2018-07-11  3:12                           ` Larry McVoy
2018-07-13  9:08                       ` ches@Cheswick.com
2018-07-13 14:10                         ` ron
2018-07-10 14:10                 ` Clem Cole
2018-07-03 17:34       ` Perry E. Metzger
2018-06-29 23:55 ` Dave Horsfall
2018-06-30  0:06   ` Greg 'groggy' Lehey
2018-06-30 14:20   ` John P. Linderman

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=FC992FEB-FF0F-48DD-A7BC-2F41C3B98B88@planet.nl \
    --to=pnr@planet.nl \
    --cc=tuhs@minnie.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).