The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] Early Internet work
Date: Fri, 17 Feb 2017 09:06:15 -0800	[thread overview]
Message-ID: <20170217170615.GR20932@mcvoy.com> (raw)
In-Reply-To: <20170217165143.3B16B18C092@mercury.lcs.mit.edu>

This is some fascinating reading.  Read the stuff in ports/ipc.

On Fri, Feb 17, 2017 at 11:51:43AM -0500, Noel Chiappa wrote:
>     > OK, we're starting to get through all the clearances needed to release
>     > the non-MIT Unix systems
> 
> We have now completed (as best we can) the OK's for the 'BBN TCP/IP V6 Unix',
> and I finally bestirred myself to add in the documentation I found for it,
> and crank out a tarball, available here:
> 
>   http://ana-3.lcs.mit.edu/~jnc/tech/pdp11/tmp/bbn.tar
> 
> It includes all the documentation files I found for the Rand and BBN code (in
> the ./doc directory); included are the original NROFF source to the two Rand
> publications about ports, and several BBN reports.
> 
> This is an early TCP/IP Unix system written at BBN. It was not the first
> TCP/IP Unix; that was one done at BBN in MACRO-11, based on a TCP done in
> MACRO-11 by Jim Mathis at SRI for the TIU (Terminal nterface Unit).
> 
> This networking code is divided into three main groups. First there is
> code for the kernel, which includes IPC enhancements to Unix, including
> Rand ports, as well as further extensions to that done at BBN for the
> earlier TCP - the capac() and await() calls. It also includes a IMP
> interface driver (the code only interfaced to the ARPANET at this point in
> time). Next, TCP is implemented as a daemon which ran as a single process
> which handled all the connections. Finally, other programs implement
> applications; TELNET is the only one provided at this point in time.
> 
> The original port code was written by Steven Zucker at Rand; the extensions
> done at BBN were by Jack Haverty. The TCP was mostly written by Mike
> Wingfield, apparently with some assistance by Jon Dreyer. Dan Franklin
> apparently wrote the TELNET.
> 
> 
> Next, I'll be working on the MIT-CSR machine. That's going to take quite a
> while - it's a whole system, with a lot of applications. It does include FTP,
> SMTP, etc, though, so it will be a good system for anyone who wants to run V6
> with TCP on a /23. We'll have to write device drivers for whatever networking
> cards are out there, though.
> 
> 	Noel

-- 
---
Larry McVoy            	     lm at mcvoy.com             http://www.mcvoy.com/lm 


  reply	other threads:[~2017-02-17 17:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 16:51 Noel Chiappa
2017-02-17 17:06 ` Larry McVoy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-02-13 23:20 Noel Chiappa
2017-02-14  7:37 ` SPC
2017-02-09  1:32 Noel Chiappa
2017-02-09  1:46 ` Dan Cross
2017-02-08 23:16 Noel Chiappa
2017-02-08 23:47 ` Charles Anthony
2017-02-09  0:37   ` Charles Anthony
2017-02-09  1:31     ` Chet Ramey
2017-02-08 18:00 Noel Chiappa

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=20170217170615.GR20932@mcvoy.com \
    --to=lm@mcvoy.com \
    /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).