From: Rob Pike <firstname.lastname@example.org>
To: Angelo Papenhoff <email@example.com>
Cc: The Eunuchs Hysterical Society <firstname.lastname@example.org>
Subject: [TUHS] Re: forgotten versions
Date: Sun, 19 Jun 2022 17:50:57 +1000 [thread overview]
Message-ID: <CAKzdPgwk+76qTKV87vYQtbiBQLGRyEo_kQj8KnAsf42JdVrJDw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2225 bytes --]
The VAX Plan 9 kernel isn't worth anything. It never worked, was never
used, and was abandoned completely when better SMP machines started
appearing. The VAX code wasn't even ported, as I remember it; Ken and I
started over from scratch with a pair of 4-core SGI machines with MIPS CPUs
and wackadoo synchronization hardware.
On Sat, Jun 18, 2022 at 5:05 PM Angelo Papenhoff <email@example.com> wrote:
> To make people more aware of post-v7 Research UNIX it would be great if
> you could actually run all of them in a simulator and have the manuals
> V8 is working perfectly in simh and there's blit (jerq) emulation as well.
> DMD 5620 emulation should be possible as well with Seth Morabito's
> emulator, but as far as I understand it needs a different ROM that we
> don't have a dump of. (I've had a real 5620 connected to my laptop
> running v8 in simh, it worked perfectly)
> V9 exists as a port to Sun-3 and it can actually be booted apparently.
> The source seems incomplete, but the VAX kernel source seems to be
> included as well. Maybe it could be gotten to run in simh on a VAX
> in some form or another?
> V10 exists but not as anything that boots. I think getting this to work
> would be the holy grail but also requires quite a bit of effort.
> I don't know if the V8 and V10 file systems are compatible, but if that
> is the case one could probably start by bootstrapping from V8.
> It also includes the multilevel-secure IX system and software for the
> 630 MTG terminal.
> As for the manual...
> The V8 files have the man pages but not much of the documents.
> The V9 files seem to have neither.
> The V10 files have both the man pages and the documents but I have not
> yet tried to troff any of this.
> Since I know at least the V10 manual to be a work of art and beauty I
> think it should be available to everyone. I have not seen the physical
> V8 and V9 manuals, but if they look anything like the V10 one, they too
> deserve to be available to the public.
> Does anyone have a plan of attack? I'd gladly join some effort to make
> the research systems more visible or available again (but probably don't
> have the motivation to do so alone).
[-- Attachment #2: Type: text/html, Size: 2711 bytes --]
next prev parent reply other threads:[~2022-06-19 7:51 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 23:06 [TUHS] " Rob Pike
2022-06-16 23:17 ` [TUHS] " Earl Baugh
2022-06-16 23:18 ` George Michaelson
2022-06-16 23:44 ` George Michaelson
2022-06-17 0:10 ` Larry McVoy
2022-06-17 16:23 ` [TUHS] Sockets vs Streams (was " Bakul Shah
2022-06-17 17:43 ` [TUHS] " Paul Winalski
2022-06-17 22:52 ` Dan Stromberg
2022-06-17 7:20 ` [TUHS] " Diomidis Spinellis
2022-06-17 7:33 ` Rob Pike
2022-06-17 8:34 ` arnold
2022-06-17 10:52 ` arnold
2022-06-18 7:05 ` Angelo Papenhoff
2022-06-19 7:50 ` Rob Pike [this message]
2022-06-19 8:17 ` Angelo Papenhoff
2022-06-19 8:53 ` Rob Pike
2022-06-19 9:02 ` Angelo Papenhoff
2022-06-19 9:14 ` arnold
2022-06-19 9:19 ` Angelo Papenhoff
2022-06-19 9:23 ` arnold
2022-06-19 11:37 ` Matthias Bruestle
2022-06-19 14:47 ` Kenneth Goodwin
2022-06-19 16:27 ` Al Kossow
2022-06-19 18:32 ` Theodore Ts'o
2022-06-19 18:38 ` Dan Cross
2022-06-21 23:56 ` Jacob Moody
2022-06-22 0:13 ` Larry McVoy
2022-06-22 0:48 ` Rob Pike
2022-06-22 1:55 ` George Michaelson
2022-06-22 2:10 ` Bakul Shah
2022-06-22 2:14 ` Jon Steinhart
2022-06-22 2:19 ` Andrew Hume
2022-06-22 2:58 ` Rob Pike
2022-06-22 3:09 ` George Michaelson
2022-06-22 2:16 ` Andrew Hume
2022-06-22 2:55 ` Brad Spencer
2022-06-17 14:50 Paul Ruizendaal
2022-06-18 0:35 Douglas McIlroy
2022-06-18 5:00 ` Kevin Bowling
2022-06-18 5:13 ` Adam Thornton
2022-06-18 16:58 ` Clem Cole
2022-06-18 17:18 ` Warner Losh
2022-06-18 17:57 ` Clem Cole
2022-06-18 19:55 Paul Ruizendaal
2022-06-22 12:06 Noel Chiappa
2022-06-23 0:02 ` Dan Cross
2022-06-23 2:18 Noel Chiappa
2022-06-24 6:47 Paul Ruizendaal
2022-06-25 19:16 ` Anthony Martin
2022-06-25 20:45 ` Paul Ruizendaal
2022-06-27 0:57 ` Kevin Bowling
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).