The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Unix with TCP/IP for small PDP-11s
Date: Fri, 19 May 2017 18:21:01 -0600	[thread overview]
Message-ID: <CANCZdfoibU4ftDtz_zkvb675-=Q9a7jy=vnugF-07it7=gJPRg@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfoCMEVG69=fHNHhxv=K=6xBe33kFWxYNUM+uSxKP0a2Ug@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]

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.

Warner



On Fri, May 19, 2017 at 6:15 PM, Warner Losh <imp at bsdimp.com> wrote:

> There's a copy of ultrix-11, which is v7 based with some 4.1BSD additions,
> including sockets and a TCP/IP stack. Don't know if it runs on the smaller
> PDP-11, but it looks like it might. The sources are in the TUHS archives.
> Seems like the best low-end v7ish kernel with TCP/IP around, but I've not
> used it extensively.
>
> Warner
>
> On Fri, May 19, 2017 at 1:04 PM, Ron Natalie <ron at ronnatalie.com> wrote:
>
>> To my knowledge no.   We had already gone to code overlays on the 11/34’s
>> just to get the pre-TCP unix working.    When we needed yet another segment
>> to map mbufs (which we could do on the 11/70), there just weren’t any
>> left.      It was then that I scarfed up all the 11/23, 24, 34’s that were
>> available and turned them into routers.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170519/a381ab39/attachment.html>


  reply	other threads:[~2017-05-20  0:21 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
     [not found] <mailman.1.1495245601.20449.tuhs@minnie.tuhs.org>
2017-05-20 10:46 ` Johnny Billquist
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-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-23  1:14 Noel Chiappa
2017-05-23  1:33 Noel Chiappa
2017-05-23 11:35 Paul Ruizendaal
2017-05-23 13:43 Noel Chiappa
     [not found] <mailman.1.1495591202.25149.tuhs@minnie.tuhs.org>
2017-05-24  9:20 ` Paul Ruizendaal
2017-05-24 15:21 Noel Chiappa
2017-05-24 17:19 ` Jeremy C. Reed

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='CANCZdfoibU4ftDtz_zkvb675-=Q9a7jy=vnugF-07it7=gJPRg@mail.gmail.com' \
    --to=imp@bsdimp.com \
    /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).