From: Bakul Shah <bakul@iitbombay.org>
To: Larry McVoy <lm@mcvoy.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Fwd: [simh] Announcing the Open SIMH project
Date: Fri, 3 Jun 2022 19:59:54 -0700 [thread overview]
Message-ID: <DF31148F-E6B1-4300-844C-1447CE522828@iitbombay.org> (raw)
On Jun 3, 2022, at 4:48 PM, Larry McVoy <lm@mcvoy.com> wrote:
> Um, so there were 3: 386, Net and Free. That's already 2 too many.
My recollection matches what Warner is saying. NetBSD &
FreeBSD got going *because* 386BSD was effectively frozen. It
wasn't dead dead but patches were not being upstreamed (as we
say now), and so on. I do agree with you that even two variants
were 1 too many. But even one would probably not have mattered
as the AT&T lawsuit was a huge cloud on *BSD's popularity. As
well as there were other factors. Linus and Linux had a much
better story, its development was more nimble, with many younger
and much more enthusiastic developers/users etc.
Not that anyone really cares at this point except some graybeards!
The Open SIMH project sounds great!
next reply other threads:[~2022-06-04 3:00 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-04 2:59 Bakul Shah [this message]
[not found] <BCDAF4C4-12EC-49D6-84A6-4592E245922F@comcast.net>
[not found] ` <CAC20D2NGMK1NG3J+iR8t2rAzOc2uWCe9ZGRJzkZn6ECgMETJEQ@mail.gmail.com>
[not found] ` <CAC20D2OK9muQm=gCSeRzarV_HQF6vZ9VNuYRas4uCbMyxYKjJA@mail.gmail.com>
2022-06-03 20:00 ` [TUHS] " Clem Cole
2022-06-03 20:12 ` [TUHS] " Blake McBride
2022-06-03 20:23 ` G. Branden Robinson
2022-06-03 21:06 ` Clem Cole
2022-06-03 21:20 ` Tom Ivar Helbekkmo via TUHS
2022-06-03 21:32 ` Larry McVoy
2022-06-03 21:34 ` Tom Ivar Helbekkmo via TUHS
2022-06-03 21:37 ` Larry McVoy
2022-06-03 21:36 ` Tom Ivar Helbekkmo via TUHS
2022-06-03 21:40 ` Larry McVoy
2022-06-03 22:16 ` Tom Ivar Helbekkmo via TUHS
2022-06-03 22:30 ` Larry McVoy
2022-06-03 22:52 ` Warner Losh
2022-06-03 23:48 ` Larry McVoy
2022-06-04 0:10 ` Warner Losh
2022-06-04 1:05 ` Larry McVoy
2022-06-04 1:46 ` David Arnold
2022-06-06 0:32 ` Theodore Ts'o
2022-06-06 0:47 ` George Michaelson
2022-06-06 1:17 ` Larry McVoy
2022-06-06 1:02 ` Warner Losh
2022-06-06 1:09 ` Dan Cross
2022-06-06 1:15 ` Larry McVoy
2022-06-06 1:40 ` Dan Cross
2022-06-06 2:36 ` Larry McVoy
2022-06-06 12:43 ` Dan Cross
2022-06-06 13:41 ` Larry McVoy
2022-06-06 14:27 ` Blake McBride
2022-06-06 14:33 ` Steve Nickolas
2022-06-06 14:53 ` Henry Bent
2022-06-06 23:28 ` David Arnold
2022-06-07 14:30 ` Theodore Ts'o
2022-06-07 15:08 ` Dan Cross
2022-06-07 15:25 ` Larry McVoy
2022-06-07 16:03 ` Will Senn
2022-06-07 16:38 ` Warner Losh
2022-06-07 16:45 ` Larry McVoy
2022-06-07 16:57 ` Warner Losh
2022-06-07 17:05 ` Larry McVoy
2022-06-07 16:46 ` Blake McBride
2022-06-07 17:26 ` Paul Winalski
2022-06-07 20:09 ` Blake McBride
2022-06-07 17:00 ` Paul Winalski
2022-06-07 15:55 ` Richard Salz
2022-06-03 23:56 ` David Arnold
2022-06-04 0:30 ` Yeechang Lee
2022-06-04 1:03 ` Adam Thornton
2022-06-03 22:33 ` Warner Losh
2022-06-03 22:40 ` Tom Ivar Helbekkmo via TUHS
2022-06-03 22:56 ` Warner Losh
2022-06-03 22:26 ` Warner Losh
2022-06-03 22:19 ` Warner Losh
2022-06-03 21:35 ` Ben Walton
2022-06-03 20:52 ` Will Senn
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=DF31148F-E6B1-4300-844C-1447CE522828@iitbombay.org \
--to=bakul@iitbombay.org \
--cc=lm@mcvoy.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).