The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: A second Unix Patent
Date: Sat, 4 Mar 2023 10:08:28 -0500	[thread overview]
Message-ID: <CAC20D2MbeaM96D906RirBuGymze4YkJy6G-E6VBpjihS=poaAw@mail.gmail.com> (raw)
In-Reply-To: <20230304015746.DD95518C08D@mercury.lcs.mit.edu>

[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]

On Fri, Mar 3, 2023 at 8:58 PM Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:

> The other possible explanation is that it was perfectly possible to run
> UNIXes
> of that era (V4 on) on machines without enough main memory to hold the
> kernel
> and a 'full-sized' process simultaneously. (Our original machine, an
> -11/40,
> started out without a lot of memory; I don't recall exactly how much,
> though.
> It had, I'm pretty sure, 3 banks of core; I was thinking it was 3 MM11-L
> core
> units, which would be 3x16KB, or only 48KB, but my memory must be wrong;
> that's not really enough.)
>
It's interesting - we did the same thing at CMU - almost all of the
11/40's, 40e's and /34's we had in the 1970s running UNIX.   We would order
them with very minimalist - i.e. 48K and run UNIX swapping to RK05's
(slowly) until we had the money to buy more memory and rotating storage (
which was almost always aftermarket - not from DEC) and then those systems
would be maxed to 256K.   Mellon actually got an original RK07 cheap, so
its disks were all Digital (tape was aftermarket), but most of the Unix
boxes had dual RK05's and then some storage that we could get cheap.
  A couple
of years later, after I graduated and moved on,  I think many groups put
Enable's in a couple of them so they could break the 256K barrier - as I
sent that code back to Ted and Mike after I wrote it at Tektronix.
ᐧ

[-- Attachment #2: Type: text/html, Size: 2771 bytes --]

  parent reply	other threads:[~2023-03-04 15:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04  1:57 Noel Chiappa
2023-03-04  9:22 ` Ralph Corderoy
2023-03-04 15:08 ` Clem Cole [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-01 22:59 [TUHS] " Warner Losh
2023-03-02  4:41 ` [TUHS] " Douglas McIlroy
2023-03-02  5:16   ` David Arnold
2023-03-03 13:29   ` Steve Mynott
2023-03-03 19:19     ` James Frew

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='CAC20D2MbeaM96D906RirBuGymze4YkJy6G-E6VBpjihS=poaAw@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --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).