From: usotsuki at buric.co (Steve Nickolas)
Subject: [TUHS] Apple IIe Unix?
Date: Thu, 26 Nov 2020 22:16:52 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.2011262213300.11847@sd-119843.dedibox.fr> (raw)
In-Reply-To: <CAC20D2Oa2n5sD8uDzF2sVGTF9gWwnUKtkiCU=HKw-0vnqAOpcw@mail.gmail.com>
On Thu, 26 Nov 2020, Clem Cole wrote:
> My favorite 8-bit processor, maybe my favorite all around.
Ditto.
<snip>
> 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.
One would have better luck with the Apple IIgs except I don't think
there's a good free C compiler for 65816. There's GNO which is very BSD,
but obviously cut back for the necessity of running on top of GS/OS (and
the shell is written in asm, it's not a true Bourne shell AFAIK).
-uso.
next prev parent reply other threads:[~2020-11-27 3:16 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
2020-11-27 0:47 ` athornton
2020-11-27 3:16 ` usotsuki [this message]
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=alpine.DEB.2.21.2011262213300.11847@sd-119843.dedibox.fr \
--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).