From: bqt@update.uu.se (Johnny Billquist)
Subject: [TUHS] Unix with TCP/IP for small PDP-11s
Date: Sat, 20 May 2017 12:46:34 +0200 [thread overview]
Message-ID: <be785634-8e6b-7ede-c2eb-d8d4b475d176@update.uu.se> (raw)
In-Reply-To: <mailman.1.1495245601.20449.tuhs@minnie.tuhs.org>
On 2017-05-20 04:00, Warner Losh <imp at bsdimp.com> wrote:
> https://ia601901.us.archive.org/10/items/bitsavers_decpdp11ulLTRIX112.0SPDSep84_870730/AE-X370C-TC_ULTRIX-11_2.0SPD_Sep84.pdf
>
> Looks like it requires MMU, but not split I/D space as it lists the
> following as compatible: M11, 11/23+, 11/24, 11/34, 11/40 and 11/60. It
> does require 256kb of memory. See table 2, page 6 for details.
Uh...? Where do you see that there is any TCP/IP support in Ultrix-11?
If any was done by someone else, there is no saying that it would be
usable on a machine without split I/D. To be honest, I've never seen any
mention of TCP/IP on any machine without split I/D space. I guess it
could be done, but it would be a rather big headache...
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
next parent reply other threads:[~2017-05-20 10:46 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1495245601.20449.tuhs@minnie.tuhs.org>
2017-05-20 10:46 ` Johnny Billquist [this message]
2017-05-20 17:39 ` Henry Bent
2017-05-20 20:40 ` Johnny Billquist
2017-05-20 20:44 ` Henry Bent
2017-05-20 18:18 ` Warner Losh
2017-05-20 19:05 ` arnold
2017-05-20 20:29 ` Warner Losh
2017-05-20 21:41 ` David Arnold
2017-05-20 21:59 ` Erik E. Fair
2017-05-20 20:40 ` Johnny Billquist
2017-05-20 21:05 ` Warner Losh
2017-05-20 21:34 ` Johnny Billquist
2017-05-21 5:13 ` Random832
2017-05-21 11:04 ` Ron Natalie
2017-05-24 15:21 Noel Chiappa
2017-05-24 17:19 ` Jeremy C. Reed
[not found] <mailman.1.1495591202.25149.tuhs@minnie.tuhs.org>
2017-05-24 9:20 ` Paul Ruizendaal
-- strict thread matches above, loose matches on Subject: below --
2017-05-23 13:43 Noel Chiappa
2017-05-23 11:35 Paul Ruizendaal
2017-05-23 1:33 Noel Chiappa
2017-05-23 1:14 Noel Chiappa
2017-05-22 9:28 Paul Ruizendaal
2017-05-22 14:09 ` Clem Cole
2017-05-22 14:51 ` Steve Simon
2017-05-22 16:29 ` Clem Cole
2017-05-22 16:35 ` Ron Natalie
2017-05-22 22:07 ` Paul Ruizendaal
2017-05-22 23:25 ` Clem Cole
2017-05-23 0:36 ` Paul Ruizendaal
2017-05-19 15:15 Noel Chiappa
2017-05-19 16:29 ` Henry Bent
2017-05-19 19:04 ` Ron Natalie
2017-05-20 0:15 ` Warner Losh
2017-05-20 0:21 ` Warner Losh
2017-05-19 17:39 ` Clem Cole
2017-05-21 16:16 ` Dave Horsfall
2017-05-21 19:58 ` Clem Cole
2017-05-21 20:57 ` Ron Natalie
2017-05-21 21:26 ` Clem Cole
2017-05-21 21:46 ` William Pechter
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=be785634-8e6b-7ede-c2eb-d8d4b475d176@update.uu.se \
--to=bqt@update.uu.se \
/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).