From: Dan Cross <crossd@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: forgotten versions
Date: Sun, 19 Jun 2022 14:38:26 -0400 [thread overview]
Message-ID: <CAEoi9W7QQEQyhBFv-uf2v2AMBX3cL4tjcqAvvY+pK8gHSz+qqA@mail.gmail.com> (raw)
In-Reply-To: <Yq9rzRUNIFmsnsFT@mit.edu>
On Sun, Jun 19, 2022 at 2:33 PM Theodore Ts'o <tytso@mit.edu> wrote:
> On Sun, Jun 19, 2022 at 10:47:23AM -0400, Kenneth Goodwin wrote:
> > 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.
>
> I'll second that. I think it would be really helpful.
>
> There was a time when I was reviewing a paper which made a bunch of
> claims about what Plan 9 was trying to accomplish and in particular
> about what the ultimate design goals for a particular component of
> Plan 9. (I won't go into further details since as far as I know, that
> paper was never published.)
>
> In any case, since I wasn't familiar with the history of Plan 9 to
> evaluate these claims, with the permission of the PC chairs, I found
> someone who had been part of the Plan 9 team, and asked them to review
> certain passages for accuracy, and they said, "Uh, no.... that's
> totally not the case. They're completely wrong."
>
> So if someone were willing to create additional write ups about
> lessons learned, or if that's too much work, maybe someone could do
> some interview for a podcast or a vlog, that would be really
> excellent.
Agreed. A retrospective would be a very welcome addition to the canon.
- Dan C.
(PS: I _had_ heard of the VAX effort before, but I don't think I'd known
quite how nascent it was before it was abandoned in favor of MIPS and
68k.)
next prev parent reply other threads:[~2022-06-19 18:39 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
2022-06-19 16:27 ` Al Kossow
2022-06-19 18:32 ` Theodore Ts'o
2022-06-19 18:38 ` Dan Cross [this message]
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=CAEoi9W7QQEQyhBFv-uf2v2AMBX3cL4tjcqAvvY+pK8gHSz+qqA@mail.gmail.com \
--to=crossd@gmail.com \
--cc=tuhs@tuhs.org \
--cc=tytso@mit.edu \
/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).