The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Ruizendaal <pnr@planet.nl>
To: TUHS main list <tuhs@minnie.tuhs.org>, Lars Brinkhoff <lars@nocrew.org>
Subject: Re: [TUHS] Unix NCP protocol stack for ARPANET
Date: Mon, 25 Oct 2021 18:50:26 +0200	[thread overview]
Message-ID: <773CD17C-9ACC-461E-BDE3-DBB5AB00E20F@planet.nl> (raw)

> I have searched the TUHS archive and elsewhere, but all I
> find for Unix is a copy of the PDP-11 Unix V6 NCP from Illinois.
> 
> Has any other NCP implementation for Unix survived?  From old host
> tables I think there may have been some VAXen online before the switch
> to TCP/IP.

Lars,

You may want to look at the 4 surviving BBN tapes on Kirk McKusick’s DVD software collection. A small part of that is on the TUHS Unix tree page - see the 4.1BSD entry.

1. A history of NCP on the VAX at BBN can be found in the change log:
https://www.tuhs.org/cgi-bin/utree.pl?file=BBN-Vax-TCP/history

In short they started with 32V in the Fall of 1979, and ported UIUC’s NCP code to it in May 1980. They then moved to 4.1BSD in August and ported yet again. It would seem that the ports were fairly straightforward. Coding for TCP begins in January 1981.

2. Note that the BBN TCP worked over NCP as its primary transport. The driver is still there if you look through the surviving BBN tapes. Part of that code is on TUHS:
https://www.tuhs.org/cgi-bin/utree.pl?file=BBN-Vax-TCP/dev/acc.c
https://www.tuhs.org/cgi-bin/utree.pl?file=BBN-Vax-TCP/bbnnet-oct82/imp_io.c

It will take some effort, but probably the NCP VAX code can be reconstructed from the surviving PDP11 UIUC code and these BBN tapes (the file names in the change log match).

3. The BBN tapes also have some user level software: telnet, ftp, mtp. This code consists of straight NCP to TCP conversions and the source code has #ifdef’s for NCP and TCP. An example is here:
https://www.tuhs.org/cgi-bin/utree.pl?file=BBN-Vax-TCP/src/telnet/netser.c

Hope this helps.

Paul

PS - Info on the DVD is here (bottom of the page):
https://www.mckusick.com/csrg/


             reply	other threads:[~2021-10-25 16:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 16:50 Paul Ruizendaal [this message]
2021-10-25 19:04 ` Lars Brinkhoff
  -- strict thread matches above, loose matches on Subject: below --
2021-10-26  8:06 Paul Ruizendaal
2021-10-25 18:50 Noel Chiappa
2021-10-28  9:41 ` Lars Brinkhoff
2021-10-24 16:16 Lars Brinkhoff
2021-10-24 17:24 ` Clem Cole
2021-10-24 18:32   ` Ron Natalie
2021-10-24 19:28     ` Clem Cole
2021-10-24 19:28     ` Warner Losh
2021-10-24 20:25       ` Clem Cole
2021-10-25  9:26   ` Lars Brinkhoff

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=773CD17C-9ACC-461E-BDE3-DBB5AB00E20F@planet.nl \
    --to=pnr@planet.nl \
    --cc=lars@nocrew.org \
    --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).