From: Ed Carp <erc@pobox.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Happy birthday, 386BSD!
Date: Sun, 14 Jul 2019 00:13:35 -0700 (MST) [thread overview]
Message-ID: <alpine.DEB.2.00.1907140008320.2131@seddev1> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1907141555310.53965@aneurin.horsfall.org>
On Sat, 13 Jul 2019, space aliens made Dave Horsfall write:
> 386BSD was released on this day in 1992, when William and Lynne Jolitz
> started the Open Source movement; well, that's what my notes say, and
Not really. Bill and Lynne kept very tight control over releases - the
word "open" didn't really apply to 386BSD, and there were many Open Source
projects well under way before 386BSD was even conceived.
Under Linux, the process was a lot more "open", even democratic. One of
the reasons I abandoned 386BSD early on and started working on Linux was
because I (as well as many others) were very frustrated at the complete
contol the Jolitz's exercised over 386BSD, and limited releases to one
every six months - much slower than was generally considered to be
acceptable for the long list of bugs and fixes in the pipeline.
next prev parent reply other threads:[~2019-07-14 7:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-14 5:56 Dave Horsfall
2019-07-14 6:01 ` Larry McVoy
2019-07-14 7:15 ` Ed Carp
2019-07-14 8:14 ` Jason Stevens
2019-07-14 6:15 ` Greg 'groggy' Lehey
2019-07-14 6:23 ` Greg 'groggy' Lehey
2019-07-17 0:38 ` Jason Stevens
2019-07-14 6:53 ` Jason Stevens
2019-07-14 8:17 ` [TUHS] Thanks for Virtuallyfun! (was Re: Happy birthday, 386BSD!) Michael Huff
2019-07-14 9:07 ` Jason Stevens
2019-07-14 17:47 ` Adam Thornton
2019-07-15 1:54 ` Jason Stevens
2019-07-14 7:13 ` Ed Carp [this message]
2019-07-14 12:52 ` [TUHS] Happy birthday, 386BSD! Theodore Ts'o
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=alpine.DEB.2.00.1907140008320.2131@seddev1 \
--to=erc@pobox.com \
--cc=dave@horsfall.org \
--cc=ecarp@lsisoft.net \
--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).