The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Lars Brinkhoff <lars@nocrew.org>
To: Michael Casadevall <michael@casadevall.pro>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Attempting To Build NOSC and BBN UNIXs + ARPANET code
Date: Mon, 10 Oct 2022 19:48:14 +0000	[thread overview]
Message-ID: <7wbkqjmpdt.fsf@junk.nocrew.org> (raw)
In-Reply-To: <CAEMRDeG90fL81OWfFyNZNqVaC1ZHJGcNUTgvEDqcuR8yiLqrsQ@mail.gmail.com> (Michael Casadevall's message of "Mon, 10 Oct 2022 14:33:25 -0400")

Michael Casadevall wrote:
> part of impio.c is cut off. However, this isn’t quite as bad as it
> sounds. For example, by kitbashing both the original v6 source code,
> and the later BBN TCP code, I was able to create a sys4.c that builds
> and links which should be close to the original. Furthermore, it is
> possible to use the “vdh” target instead of the imp target to at least
> try and get the code building.

Too bad about impio.c!  Maybe something can be extracted from the
unix.greg binary?  I see there's also the ACC interface, another
alternative to IMP11A.

> My guess is it's either deadlocked waiting for the IMP, or there’s
> something wrong with the build.

Since you don't have anything backing the hardware registers for the IMP
interface, it seems likely something will be upset.

> Furthermore, I do know that I can run some of the ARPA level utilities
> in MIT ITS on CHAOSNET, which will be an upcoming project, although
> that is going to be a dive in and of itself.

It's complicated.  Many of the utilities have parallels between the two,
and some work on both.  And there's a server to provide a gateway from
Chaosnet to Arpanet.  Give me a ping when you're looking into ITS.

> I know IMPs have been emulated, and even have successfully routed
> packets, so I’m also trying to figure out how much would still be
> necessary to actually recreate a minimal ARPA network?

Reviving the host software, like you are are doing, is one vital part of
it.  Another it adding emulators for various IMP interfaces.  I.e. you
will not get anywhere without adding one of IMP11A, ACC, or VDH to SIMH.

For adding other nodes to the network, PDP-10 hosts are your best bet.
There isn't much else left.

  reply	other threads:[~2022-10-10 19:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-10 18:33 [TUHS] " Michael Casadevall
2022-10-10 19:48 ` Lars Brinkhoff [this message]
2022-10-10 20:31   ` [TUHS] " 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
2022-10-11 15:08 Paul Ruizendaal
2022-10-12 19:38 Noel Chiappa
2022-10-13  5:50 ` Lars Brinkhoff
2022-10-14 11:55 Paul Ruizendaal
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
2022-10-14 20:30 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=7wbkqjmpdt.fsf@junk.nocrew.org \
    --to=lars@nocrew.org \
    --cc=michael@casadevall.pro \
    --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).