From: doug@cs.dartmouth.edu (Doug McIlroy)
Subject: [TUHS] File-as-record
Date: Tue, 12 Sep 2017 07:18:52 -0400 [thread overview]
Message-ID: <201709121118.v8CBIqwn029754@coolidge.cs.Dartmouth.EDU> (raw)
> On the programming side, there wasn't either the memory capacity or
> processing power to implement a modern disk file system. One of the
> first computers I worked with was a System/360 model 25 running
> DOS/360. The machine had 48K of core memory, 12K of which was for the
> OS, leaving 36K for programs. No virtual memory.
Unix was a counterexample. Recall that v1 worked on a 24K
machine, 16K of which was OS and 8K user. And it had a modern
file system. Programming was so much easier that it lured
people (e.g. me) away from big mainframe computers.
Doug
next reply other threads:[~2017-09-12 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 11:18 Doug McIlroy [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-08 20:54 [TUHS] Happy birthday, Dennis Ritchie! Dave Horsfall
2017-09-08 21:04 ` Noel Chiappa
2017-09-08 21:09 ` Michael Kjörling
2017-09-09 1:16 ` Wesley Parish
2017-09-09 1:30 ` [TUHS] File-as-record (was: Happy birthday, Dennis Ritchie!) Greg 'groggy' Lehey
2017-09-09 1:50 ` Wesley Parish
2017-09-09 13:59 ` [TUHS] File-as-record Arthur Krewat
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=201709121118.v8CBIqwn029754@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).