From: clemc at ccc.com (Clem Cole)
Subject: [TUHS] Apple IIe Unix?
Date: Thu, 26 Nov 2020 18:00:22 -0500 [thread overview]
Message-ID: <CAC20D2Oa2n5sD8uDzF2sVGTF9gWwnUKtkiCU=HKw-0vnqAOpcw@mail.gmail.com> (raw)
In-Reply-To: <c2d6b3fa-df83-5efe-03a7-77b09bc82667@gmail.com>
On Thu, Nov 26, 2020 at 4:56 PM Will Senn <will.senn at gmail.com> wrote:
> Hi All,
>
> So, I'm about to get my very own Apple IIe and while it's an incredibly
> versatile machine for assembly language and hardware hackery, I'm not aware
> of any Unices that run on the machine, natively. Does anybody know of any
> from back in the day?
>
> It's got a 65c02 processor and somewhere around 128k of RAM, but it's also
> pretty expandable w/7 slots and a huge amount of literature about how to do
> stuff w/those slots.
>
My favorite 8-bit processor, maybe my favorite all around. So simple, one
accumulator and two index registers but it is only 64K of total address -
although with bank switching more memory could be added in 4K banks on a
number of Apple II's, but you have 16 address bits and worked a register
that switched in and out the 4K banks. and there is of course no protection
hardware nor the concept of user/kernel in the hardware. The size of the
Apple Floppy disk was rather small, and your need 3 to run things like the
UCSD Pascal system to have any experience other than constantly switching
disks.
There are a number of C compilers available but with its limited and fixed
stack (8 bits only), so it is difficult to run programs of any size (in any
language - automatics are often managed off the stack).
Running a full UNIX on it was not really possible although a few of the
Unix style utilities were moved to it and a number of simple monitors were
written that swapped programs in and out DOS style. At one time, I had a
fairly good version of the Bourne (V7) syntax shell we got running, but it
had to be swapped in and out slowly. That is; you run the shell, type a
command, when exec is done, the shell is tossed out and the new program
installed in memory.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20201126/7ee7bb6d/attachment.htm>
next prev parent reply other threads:[~2020-11-26 23:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2020-11-27 11:54 jnc
2020-11-27 12:20 ` usotsuki
2020-11-27 16:22 ` cowan
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
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='CAC20D2Oa2n5sD8uDzF2sVGTF9gWwnUKtkiCU=HKw-0vnqAOpcw@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).