From: Kevin Bowling <kevin.bowling@kev009.com>
To: Al Kossow <aek@bitsavers.org>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Fwd: Anyone have Plexus docs/software squirreled away?
Date: Wed, 19 Jun 2024 15:25:10 -0700 [thread overview]
Message-ID: <CAK7dMtBd0Uz3C8yHBaUN8p_z+B_JN+yqJuu8oMuH7jKe3FgkVg@mail.gmail.com> (raw)
In-Reply-To: <58cc45a9-d1b0-9dba-c3c0-a2970c4d7b3d@bitsavers.org>
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
On Thu, Jun 20, 2024 at 12:07 AM Al Kossow <aek@bitsavers.org> wrote:
>
>
> FYI, for people like me that care about 80s 68K Unix systemf
> There is a pretty serious multi-purpose preservation effort that started a
> few weeks ago
> around Plexus systems as a result of a series of YouTube videos
>
> https://youtu.be/iltZYXg5hZw
> https://github.com/misterblack1/plexus-p20/
Seems like yet another mediocre UNIX port at first, but then they happen to
find the system schematic netlists and PAL equations in addition to partial
source code on the hard disk. If those are published that will make a
quite wholesome thing to study.
[-- Attachment #2: Type: text/html, Size: 1145 bytes --]
next prev parent reply other threads:[~2024-06-19 22:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d949c87a-01ae-08d3-eee0-871f5975d935@bitsavers.org>
2024-06-19 16:07 ` [TUHS] " Al Kossow
2024-06-19 16:20 ` [TUHS] " Steve Nickolas
2024-06-19 17:22 ` Al Kossow
2024-06-19 22:13 ` Grant Taylor via TUHS
2024-06-19 22:25 ` Kevin Bowling [this message]
2024-06-19 22:46 ` Al Kossow
2024-06-19 22:58 ` Kevin Bowling
2024-06-19 23:03 ` Rik Farrow
2024-06-19 23:10 ` Al Kossow
2024-06-19 23:21 ` [TUHS] " Peter Yardley
2024-06-20 0:20 ` Warner Losh
2024-06-20 1:18 ` Peter Yardley
2024-06-20 2:30 ` Henry Bent
2024-06-20 2:48 ` Warner Losh
2024-06-20 4:12 ` segaloco via TUHS
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=CAK7dMtBd0Uz3C8yHBaUN8p_z+B_JN+yqJuu8oMuH7jKe3FgkVg@mail.gmail.com \
--to=kevin.bowling@kev009.com \
--cc=aek@bitsavers.org \
--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).