From: Warner Losh <imp@bsdimp.com>
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] 2.9bsd with networking on 18-bit possible?
Date: Mon, 10 Dec 2018 20:28:02 -0700 [thread overview]
Message-ID: <CANCZdfpW9fDU5oK4DjxF2MW5M_zSP+T_-u1dG0j=o4kP69OXuQ@mail.gmail.com> (raw)
In-Reply-To: <369b368b-9bac-827f-6383-37c62a6b87d7@spamtrap.tnetconsulting.net>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
On Mon, Dec 10, 2018 at 7:37 PM Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
wrote:
> On 12/10/18 7:11 PM, Noel Chiappa wrote:
> > NCP was turned off on 1 January, 1983. What do you think?a
>
> I don't know 2.9BSD's time frame (and did not look it up) so I can't say
> one way or the other.
>
> Based on your response I'm going to assume that it's not possible.
>
I kinda doubt it has good NCP support: it was released in November of 1983.
> > Such as?
>
> I'd have to go back and look, but I think I have read about an NCP and
> IP speaking host in the last few months. It may have been related to
> MULTICS.
>
> The idea is that it might be simpler to speak TCP/IP to such a machine
> and then connect from it to 2.9BSD, if 2.9BSD supported NCP.
>
> If the OPs goal is to get network connectivity on an 18-bit PDP, then
> that might be another option that doesn't require shoehorning TCP/IP
> into said PDP.
>
I'd get it running in simh, then move to real hardware. It's going to take
a lot of elbow grease to make that work, I think. But I haven't looked in
detail at things.
Ultrix-11 is of similar vintage, and similar functionality and does boot on
the 18-bit 11's.
Warner
[-- Attachment #2: Type: text/html, Size: 1810 bytes --]
next prev parent reply other threads:[~2018-12-11 3:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 2:11 Noel Chiappa
2018-12-11 2:36 ` Grant Taylor via TUHS
2018-12-11 3:28 ` Warner Losh [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-15 1:54 Paul Ruizendaal
2018-12-12 17:55 Paul Ruizendaal
2018-12-12 14:38 Noel Chiappa
2018-12-12 14:14 Noel Chiappa
2018-12-12 10:29 Paul Ruizendaal
2018-12-11 18:43 Noel Chiappa
2018-12-11 18:51 ` Clem Cole
2018-12-12 1:20 ` Jacob Ritorto
2018-12-11 16:57 Noel Chiappa
2018-12-11 17:01 ` Jon Forrest
2018-12-11 18:03 ` Clem Cole
2018-12-11 16:16 Noel Chiappa
2018-12-11 16:26 ` Clem Cole
2018-12-11 4:42 Noel Chiappa
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
2018-12-11 15:28 ` Clem Cole
2018-12-11 17:21 ` 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='CANCZdfpW9fDU5oK4DjxF2MW5M_zSP+T_-u1dG0j=o4kP69OXuQ@mail.gmail.com' \
--to=imp@bsdimp.com \
--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).