From: doug@cs.dartmouth.edu (Doug McIlroy)
Subject: [TUHS] Kernel Sizes
Date: Sun, 21 Jan 2018 17:36:05 -0500 [thread overview]
Message-ID: <201801212236.w0LMa5qG013807@coolidge.cs.Dartmouth.EDU> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
> I seem to remember that at some point early on, we spent some of our
> capital budget on buying another 16K bytes for the PDP-11. As I
> recall, the deal was that the OS got 8K and users got 8K. I also
> recall that that purchase was 20% of our capital budget for the
> year...
> Doug, did I remember this correctly?
> Steve
Things did happen that way. I don't specifically remember the
numbers, but those you state have the ring of truth.
Memory came in (expensive) 4K increments. When the keepers of
Unix in the Charlotte wire center wanted to add 4K, their
management consented only on the condition that the wizards
in Research would confirm that roposed new functionality
really required it.
doug
next reply other threads:[~2018-01-21 22:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 22:36 Doug McIlroy [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-22 10:46 Rudi Blom
[not found] <mailman.4.1516572202.3873.tuhs@minnie.tuhs.org>
2018-01-21 23:42 ` Paul Ruizendaal
2018-01-21 22:03 Doug McIlroy
2018-01-20 18:11 Warner Losh
2018-01-20 18:33 ` Donald ODona
2018-01-20 19:22 ` Random832
2018-01-20 21:14 ` Michael Kjörling
2018-01-21 0:19 ` Warren Toomey
2018-01-21 1:41 ` Andy Kosela
2018-01-22 3:51 ` Warner Losh
2018-01-22 4:39 ` Grant Taylor
2018-01-22 6:53 ` Warner Losh
2018-01-21 2:08 ` Dan Stromberg
2018-01-21 2:13 ` Steve Johnson
2018-01-21 4:24 ` Warner Losh
2018-01-21 22:53 ` Greg 'groggy' Lehey
2018-01-22 1:19 ` Steve Nickolas
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=201801212236.w0LMa5qG013807@coolidge.cs.Dartmouth.EDU \
--to=doug@cs.dartmouth.edu \
/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).