The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Ruizendaal <pnr@planet.nl>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Attempting To Build NOSC and BBN UNIXs + ARPANET code
Date: Fri, 14 Oct 2022 13:55:54 +0200	[thread overview]
Message-ID: <9AA075C9-995F-47F7-9758-2492407DC9FF@planet.nl> (raw)

[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]

Maybe I’m dim, but I’ve lost track in this discussion of what is missing / corrupted.

sys4.c: I think this is available in BBN V6:
https://minnie.tuhs.org/cgi-bin/utree.pl?file=BBN-V6/ken <https://minnie.tuhs.org/cgi-bin/utree.pl?file=BBN-V6/ken>
In this file the only real network addition is Jack Haverty’s user timer variable, I think. What else is missing?

imp11a.c: available in two versions here:
https://minnie.tuhs.org/cgi-bin/utree.pl?file=BBN-V6/dmr <https://minnie.tuhs.org/cgi-bin/utree.pl?file=BBN-V6/dmr>

impio.c: available here:
https://minnie.tuhs.org/cgi-bin/utree.pl?file=BBN-V6/ncpkernel/impio.c <https://minnie.tuhs.org/cgi-bin/utree.pl?file=BBN-V6/ncpkernel/impio.c>

Maybe the compiler has a different opinion, but they don’t look obviously corrupted [??]

Also, the BBN-VAX files may be a solution. BBN sent four tapes with snap shots to CSRG in 1981. The TUHS website has the newest version, but there are 3 older ones (all 4 come from Kirk McKusick’s DVD set). They all have a slightly different set of files. These tapes also have IMP and ACC drivers in them, along with a token ring driver that was apparently based on Noel’s work back in the day. These files may also help filling in blank spots in PDP11 files.

Paul



[-- Attachment #2: Type: text/html, Size: 1974 bytes --]

             reply	other threads:[~2022-10-14 11:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 11:55 Paul Ruizendaal [this message]
2022-10-14 16:08 ` Phil Budne
2022-10-14 16:37   ` Clem Cole
2022-10-14 19:06     ` Warner Losh
2022-10-14 18:47 ` Lars Brinkhoff
  -- strict thread matches above, loose matches on Subject: below --
2022-10-14 20:30 Noel Chiappa
2022-10-12 19:38 Noel Chiappa
2022-10-13  5:50 ` Lars Brinkhoff
2022-10-11 15:08 Paul Ruizendaal
2022-10-10 18:33 [TUHS] " Michael Casadevall
2022-10-10 19:48 ` [TUHS] " Lars Brinkhoff
2022-10-10 20:31   ` Michael Casadevall
2022-10-11  5:31     ` Lars Brinkhoff
2022-10-11 12:57       ` Michael Casadevall
2022-10-11 13:57         ` Lars Brinkhoff
     [not found]           ` <CAJq=PCV7o_kMvRLXXK9prddmyvf0hAodX+NuqqVF=49iCYt63w@mail.gmail.com>
2022-10-11 19:58             ` Lars Brinkhoff
2022-10-10 20:31 ` Clem Cole
2022-10-10 20:48   ` Michael Casadevall
2022-10-10 21:37     ` Clem Cole

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=9AA075C9-995F-47F7-9758-2492407DC9FF@planet.nl \
    --to=pnr@planet.nl \
    --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).