The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: cowan at ccil.org (John Cowan)
Subject: [TUHS] Apple IIe Unix?
Date: Fri, 27 Nov 2020 11:22:00 -0500	[thread overview]
Message-ID: <CAD2gp_S0ZotZ+0bZKdCSSFc1W6VGH3wJRtBxHA6r=BG-3dZbLw@mail.gmail.com> (raw)
In-Reply-To: <20201127115444.E581018C091@mercury.lcs.mit.edu>

On Fri, Nov 27, 2020 at 6:55 AM Noel Chiappa <jnc at mercury.lcs.mit.edu>
wrote:


> The thing that takes special hardware is _protecting_ one task from a bug
> in
> another - a bug which could trash the first tasks's (or the system's!)
> memory. One has to have memory management of some kind to do that.
>

Actually, a modified version of the * approach will also work.  When
switching processes, swap the whole process out to your fastest device (on
* this was a single write to the drum) and swap in the new process.  *
hardware had a bounds register, so it was only necessary to swap out enough
of the previous process to fit the smaller process in.  So after a while,
core started to look like an onion, with the current process at the bottom
and pieces of larger non-current processes above that.

(I thought that * was MIT CTSS, but I can't confirm that.)

As for interrupts, the stock 2e has both IRQ and NMI lines. Erann Gat aka
Ron Garret explains in <
https://www.atarimagazines.com/compute/issue9/030_1_THE_25C_APPLE_II_REAL_TIME_CLOCK.php>
how to make an external clock and hook it to the NMI pin for 25 cents in
1981 dollars (about $1.67 today; h/t measuringworth.com).



John Cowan          http://vrici.lojban.org/~cowan        cowan at ccil.org
A mosquito cried out in his pain,
"A chemist has poisoned my brain!"
The cause of his sorrow / Was para-dichloro-
Diphenyltrichloroethane.                                (aka DDT)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20201127/e252839c/attachment.htm>


  parent reply	other threads:[~2020-11-27 16:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-27 11:54 jnc
2020-11-27 12:20 ` usotsuki
2020-11-27 16:22 ` cowan [this message]
2020-11-28 23:12 ` dave
     [not found] <20201201160105.1359e68b.ref@algol>
2020-12-01 15:01 ` Jose R. Valverde via TUHS
2020-12-01 15:48   ` Will Senn
  -- strict thread matches above, loose matches on Subject: below --
2020-11-26 21:55 will.senn
2020-11-26 22:22 ` usotsuki
2020-11-26 22:30 ` nikke.karlsson
2020-11-27  0:24   ` drsalists
2020-11-26 22:47 ` dave
2020-11-26 23:07   ` katolaz
2020-11-26 23:00 ` clemc
2020-11-27  0:47   ` athornton
2020-11-27  3:16   ` usotsuki
2020-11-26 23:22 ` jason-tuhs
2020-11-27  3:18   ` usotsuki
2020-12-03 18:40 ` Chris Hanson

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='CAD2gp_S0ZotZ+0bZKdCSSFc1W6VGH3wJRtBxHA6r=BG-3dZbLw@mail.gmail.com' \
    --to=tuhs@minnie.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).