The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Kenneth Goodwin <kennethgoodwin56@gmail.com>
To: Rob Pike <robpike@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: forgotten versions
Date: Sun, 19 Jun 2022 10:47:23 -0400	[thread overview]
Message-ID: <CAMQbRb05Y-rjfhRnLV1d4-QsOSXz7zJf5oNknZn6Pt=5R5TkNg@mail.gmail.com> (raw)
In-Reply-To: <CAKzdPgymCO3oHATKgf+CMwkvsFw=zPf=7g-G-NK1RhbEP26_eg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2035 bytes --]

Just chiming in a bit..

Rob, it might be interesting to old geezers like me as well as newbies
entering the field to get a perspective on Plan 9 and its evolution. The
motivations behind it. What your group was trying to accomplish,  the
approach, pitfalls and the entire decision making process as things went
along. Even things that went horribly wrong and what happened etc.

Sorry for my potential ignorance here,  but other than the documents that
come with the source code distribution, there does not seem to be any
official textbook style document available with that level of detail going
into the evolution and back story.

I am thinking more in terms of the multics book that came out after that
project failed.

Perhaps even some college level tutorial videos on YouTube that do a deep
dive. Leaving your group's collective wisdom and insight for prosperity.
Anatomy of a Research Operating System. Approaching the Design of a modern
day distributed Operating Systems, practices and pitfalls.

(You can stop laughing 😃 now....)

On Sun, Jun 19, 2022, 4:53 AM Rob Pike <robpike@gmail.com> wrote:

> Aha, yes, my mistake, sorry about that. I bet I misread that mail because
> of the mention of a Sun port, which put me in a nostalgic (read: resentful)
> mood.
>
> Anyway, knowing about the Plan 9 VAX kernel might be interesting, but the
> kernel itself was not.
>
> -rob
>
>
> On Sun, Jun 19, 2022 at 6:17 PM Angelo Papenhoff <aap@papnet.eu> wrote:
>
>> I wasn't talking about Plan 9, but it's interesting to know that there
>> was an attempt at a VAX kernel.
>>
>> On 19/06/22, Rob Pike wrote:
>> > 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.
>> >
>> > -rob
>>
>

[-- Attachment #2: Type: text/html, Size: 2885 bytes --]

  parent reply	other threads:[~2022-06-19 14:47 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
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 [this message]
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

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='CAMQbRb05Y-rjfhRnLV1d4-QsOSXz7zJf5oNknZn6Pt=5R5TkNg@mail.gmail.com' \
    --to=kennethgoodwin56@gmail.com \
    --cc=robpike@gmail.com \
    --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).