The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@nose.cs.utoronto.ca (Norman Wilson)
Subject: [pups] V7 vs RX50 (was Getting a MicroPDP-11 Running)
Date: Thu, 27 Jul 2000 09:48:45 -0400	[thread overview]
Message-ID: <200007271351.XAA90686@minnie.cs.adfa.edu.au> (raw)

400KB floppies, or even 1.4MB ones, may seem tiny now; but they should
hardly be undersized for a bare-bones V7 root file system.  Remember
that disks weren't all that big in the late 1970s, and that one of the
important fixes in V7 was that it became possible to make a file system
bigger than 32MB.

The V7 version of the `Setting Up UNIX' paper doesn't say just how big
the root file system dump is, but the instructions say the file system
itself should have 5000 blocks: about 2.4MB.  If the dump was that big,
it would have taken just over 6 RX50 diskettes.  (But it probably wasn't
that big, because there must have been a good bit of free space in the
standard root--/tmp was there too!)

I once ran a stripped-down V7 off a single RK05 (2.5MB including swap)
for several days, during an air-conditioning crisis.  The system wasn't
fully-functional, but there was enough there to let the secretarial staff
keep up with their typing, and even run troff.

The real trouble with the RX50 is not so much the size as the speed:
the damn things are painfully slow.  I sometimes boot my V10 MicroVAXes
from RX50, as part of an experimental Jumpstart-like installation scheme.
The bare-bones installation environment requires only two floppies; the
real nuisance is that it takes several minutes to read them.

And, of course, V7 doesn't have an MSCP driver, since MSCP didn't hit the
streets until 1982 or so.

Norman Wilson



                 reply	other threads:[~2000-07-27 13:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200007271351.XAA90686@minnie.cs.adfa.edu.au \
    --to=norman@nose.cs.utoronto.ca \
    /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).