The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Lars Brinkhoff <lars@nocrew.org>
To: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
Cc: Grant Taylor <gtaylor@tnetconsulting.net>
Subject: Re: [TUHS] 2.9bsd with networking on 18-bit possible?
Date: Tue, 11 Dec 2018 07:22:47 +0000	[thread overview]
Message-ID: <7wk1kg34u0.fsf@junk.nocrew.org> (raw)
In-Reply-To: <4c0c11da-1223-ab19-72ec-4effeeb63127@spamtrap.tnetconsulting.net> (Grant Taylor via TUHS's message of "Mon, 10 Dec 2018 18:55:19 -0700")

Grant Taylor wrote:
> What protocols did 2.9BSD support?  Did it have NCP?  Or was it
> strictly serial protocols like interactive terminals / UUCP?
>
> Would it be any easier to use an external NCP to TCP/IP gateway?

It's actually a challenge to find *any* NCP software today.  I think it
would be interesting to recreate a small ARPANET.

Here's a copy of "Network Unix" from Illinois:
https://github.com/larsbrinkhoff/network-unix-v6

  reply	other threads:[~2018-12-11  7:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 22:05 Jacob Ritorto
2018-12-11  1:21 ` Clem cole
2018-12-11  1:55   ` Grant Taylor via TUHS
2018-12-11  7:22     ` Lars Brinkhoff [this message]
2018-12-11 15:28       ` Clem Cole
2018-12-11 17:21         ` Lars Brinkhoff
2018-12-11  2:11 Noel Chiappa
2018-12-11  2:36 ` Grant Taylor via TUHS
2018-12-11  3:28   ` Warner Losh
2018-12-11  4:42 Noel Chiappa
2018-12-11 16:16 Noel Chiappa
2018-12-11 16:26 ` Clem Cole
2018-12-11 16:57 Noel Chiappa
2018-12-11 17:01 ` Jon Forrest
2018-12-11 18:03 ` Clem Cole
2018-12-11 18:43 Noel Chiappa
2018-12-11 18:51 ` Clem Cole
2018-12-12  1:20   ` Jacob Ritorto
2018-12-12 10:29 Paul Ruizendaal
2018-12-12 14:14 Noel Chiappa
2018-12-12 14:38 Noel Chiappa
2018-12-12 17:55 Paul Ruizendaal
2018-12-15  1:54 Paul Ruizendaal

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=7wk1kg34u0.fsf@junk.nocrew.org \
    --to=lars@nocrew.org \
    --cc=gtaylor@tnetconsulting.net \
    --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).