From: Gregg Levine <gregg.drwho8@gmail.com>
To: tuhs@tuhs.org, Chris Hanson <cmhanson@eschatologist.net>
Subject: Re: [TUHS] Historical sources for 68010 + 68451 systems?
Date: Tue, 15 Sep 2020 19:55:52 -0400 [thread overview]
Message-ID: <CAC5iaNEvhZx_GSPww4dNpMohp_tTfUbn=LKPmVy7Raw9Z97i3g@mail.gmail.com> (raw)
In-Reply-To: <DFA6E8C5-FA9A-42AA-B46C-289E373E053A@eschatologist.net>
Hello!
Chris I have one of the later ones, a 133 in fact, and I've been
trying to find what I could run on it. Never mind a case for it, plus
power supply and stuff.... Can you share, off list of course, where
you'd gotten it?
-----
Gregg C Levine gregg.drwho8@gmail.com
"This signature fought the Time Wars, time and again."
On Tue, Sep 15, 2020 at 7:49 PM Chris Hanson <cmhanson@eschatologist.net> wrote:
>
> I have an MVME121 that I’d like to run some stuff on. I’m planning what I’ll need to do to port MINIX 1.5 but since this has a 68451 segmented MMU, I’d like to actually make use of it.
>
> Have any historical sources been published for UNIX on the various 68010 + 68451 systems from the early-mid 1980s? I’m curious how they used segmented MMUs.
>
> I figure at minimum I could have several segments set up to enforce protections and a stable per-process address space, but it’d be good to have an example.
>
> — Chris
>
next prev parent reply other threads:[~2020-09-15 23:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 23:28 Chris Hanson
2020-09-15 23:55 ` Gregg Levine [this message]
2020-09-16 3:05 ` Chris Hanson
2020-09-16 5:21 ` Arno Griffioen
2020-09-16 8:53 ` Al Kossow
2020-09-16 23:47 ` Dave Horsfall
2020-09-16 19:53 Nelson H. F. Beebe
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='CAC5iaNEvhZx_GSPww4dNpMohp_tTfUbn=LKPmVy7Raw9Z97i3g@mail.gmail.com' \
--to=gregg.drwho8@gmail.com \
--cc=cmhanson@eschatologist.net \
--cc=tuhs@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).