From: pnr@planet.nl (Paul Ruizendaal)
Subject: [TUHS] TCP/IP networking in 8th edition unix
Date: Sat, 25 Nov 2017 00:52:00 +0100 [thread overview]
Message-ID: <F4215A8C-8F16-4D23-90AA-3DC2249BF5D8@planet.nl> (raw)
In-Reply-To: <4B74ABBE-BA03-4D4B-B8C1-B3CE9A6D83CE@planet.nl>
Found a post by dmr about this in the 'net.unix-wizards' newsgroup:
https://groups.google.com/forum/#!topicsearchin/net.unix-wizards/subject$3Astreams/net.unix-wizards/b7W_j_0qASU
It would seem that my understanding of it is indeed how dmr designed it.
At the end of the post there is an example: "For example, from my machine, I can type "rlogin purdy" and connect to a Sequent machine running 4.2; the TCP connection goes over Datakit to machine "research" where it is gatewayed to a local ethernet that purdy is connected to."
I'm not quite sure how on the Sequent machine the Datakit channel would be hooked up to the 4.2BSD TCP stack. Perhaps something equivalent to e.g. 'SLiRP' was used, perhaps there was a pseudo device that hooked into the network interface layer.
Paul
Begin forwarded message:
> From: Paul Ruizendaal <pnr at planet.nl>
> Subject: TCP/IP networking in 8th edition unix
> Date: 22 November 2017 0:41:27 GMT+01:00
> To: TUHS main list <tuhs at minnie.tuhs.org>
>
>
> I'm trying to figure out how tcp/ip networking worked in 8th edition Unix.
>
> I'm starting from dmr's paper about streams (http://cm.bell-labs.co/who/dmr/st.html), the V8 man pages (http://man.cat-v.org/unix_8th/3/) and browsing the source code (tarball here http://www.tuhs.org/Archive/Distributions/Research/Dan_Cross_v8/).
>
> In the below I use 'socket' to mean a file descriptor bound to a network connection. My current understanding is like this:
>
> [... details removed ...]
> Anybody on the list with 8th edition experience who can confirm that the above understanding is about correct?
>
> Paul
>
>
>
next prev parent reply other threads:[~2017-11-24 23:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 23:41 Paul Ruizendaal
2017-11-24 23:52 ` Paul Ruizendaal [this message]
2017-11-25 21:50 ` William Cheswick
2017-11-25 23:21 ` Gregg Levine
2017-11-26 0:24 ` Brad Spencer
2017-11-26 21:28 Paul Ruizendaal
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=F4215A8C-8F16-4D23-90AA-3DC2249BF5D8@planet.nl \
--to=pnr@planet.nl \
/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).