From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] shell PS1/PS2 which survive cut-paste
Date: Thu, 7 Dec 2017 16:54:50 -0500 [thread overview]
Message-ID: <CAC20D2PjB6tM2xHPXjiLiU3Sm+r7uqs4SwSngLN0phnPB055cA@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.1712071047370.35694@aneurin.horsfall.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
On Wed, Dec 6, 2017 at 6:57 PM, Dave Horsfall <dave at horsfall.org> wrote:
>
> Never got to use the V7 shell; we were stuck with 11/40s[*]
Dave I don't understand this statement. We ran Seventh Edition on 11/40
class processors more than anything else. The issue was lack of separate
I/D space and the kernel got large so you ran out of physical memory. The
later was solved with things like the Able ENABLE, which I admit I put one
couple of 11/34 and our 11/60 (which are 11/40 class). But V7 ran fine on
it.
Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171207/c6d4cdf8/attachment.html>
next prev parent reply other threads:[~2017-12-07 21:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 1:22 George Michaelson
2017-12-06 1:28 ` Kurt H Maier
2017-12-06 2:26 ` Lyndon Nerenberg
2017-12-06 1:30 ` Steve Nickolas
2017-12-06 3:45 ` Grant Taylor
2017-12-06 5:53 ` arnold
2017-12-06 6:01 ` George Michaelson
2017-12-06 15:14 ` Ian Zimmerman
2017-12-06 6:19 ` Dave Horsfall
2017-12-06 8:00 ` arnold
2017-12-06 23:57 ` Dave Horsfall
2017-12-07 8:33 ` arnold
2017-12-07 21:46 ` Dave Horsfall
2017-12-08 6:12 ` arnold
2017-12-07 21:54 ` Clem Cole [this message]
2017-12-08 0:31 ` Dave Horsfall
2017-12-16 17:42 ` Derek Fawcus
2017-12-17 13:12 ` Don Hopkins
[not found] <mailman.402.1512547277.9955.tuhs@minnie.tuhs.org>
2017-12-06 11:02 ` Paul Ruizendaal
2017-12-06 12:00 ` arnold
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=CAC20D2PjB6tM2xHPXjiLiU3Sm+r7uqs4SwSngLN0phnPB055cA@mail.gmail.com \
--to=clemc@ccc.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).