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: Tue, 11 Oct 2022 13:57:07 +0000 [thread overview]
Message-ID: <7wczaylaz0.fsf@junk.nocrew.org> (raw)
In-Reply-To: <CAEMRDeF_P9LeyvvQ8Vs2r9R1QetFQ1BM=+T-dNgLAwNmfjX2eA@mail.gmail.com> (Michael Casadevall's message of "Tue, 11 Oct 2022 08:57:29 -0400")
Michael Casadevall wrote:
> From what I got the impression From the docs, very early ARPA, you had
> systems directly on the network, but most users had to dial into a
> specific terminal machine, which, based on the comments on the RFCs,
> was less than ideal
Sounds like a TIP, "Terminal IMP". It was an IMP with double the amount
of memory. In the upper half there was software to talk to a modem pool
for dial-in access to the network. "Less than ideal", sure. Modem
speeds were often 10-30 characters per second. Much more fun to sit at
a video terminal next to the host.
> VHD I guess was more to get more hosts online?
In some cases there was an IMP which hooked up to some local hosts, but
they also wanted to connect a computer that not in the same building but
in the area. That's when a VDH type interface was used.
> The BBN with TCP stack is a bit mislabeled: it still appears to
> support NCP, but none of the client apps are there, but its directly
> built off the NOSC stack.
That's very good. I hope the NCP support there is in good shape.
> it's probably a fork from earlier in development. 79-80 timespawn
> would have been *very* early in TCP's life
TCP had been underway since 1973. Experiments called "TCP bakeoffs"
started around 1979.
> > Pluribus IMP emulator, anyone?
>
> I do actually wonder how hard that would be.
I'm not sure. I have the impression the Pluribus computer isn't well
documented.
It might not be too hard to write an IMP replacement from scratch.
next prev parent reply other threads:[~2022-10-11 13:57 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 ` [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 [this message]
[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=7wczaylaz0.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).