The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] OT: critical Intel design flaw
Date: Thu, 4 Jan 2018 10:28:45 -0700	[thread overview]
Message-ID: <CANCZdfrG-0cmU9A6PDm72uwqcP1wS47e0rVJPotT-LiFVk6Dmg@mail.gmail.com> (raw)
In-Reply-To: <m2373lfsms.fsf@thuvia.hamartun.priv.no>

On Thu, Jan 4, 2018 at 10:20 AM, Tom Ivar Helbekkmo via TUHS <
tuhs at minnie.tuhs.org> wrote:

> Theodore Ts'o <tytso at mit.edu> writes:
>
> > The biggest problem with Jolitz's work seems to have been more social
> > than anything else.  The writeups from that era seem to indicate that
> > the Jolitz's wanted to keep a much tighter control over things, and
> > this discouraged collaboration and contributions, which led to the
> > first of *BSD fragmentation/spin-offs, starting with FreeBSD and
> > NetBSD.
>
> Indeed.  I've used NetBSD since it was called 386bsd 0.0, and the way I
> remember it, we grabbed that when Jolitz made it available, and had an
> Internet community playing with it and improving it.  Patches were
> accumulated, and sent back to Jolitz.  Then he released 0.1, with none
> of the patches from the 'net.  Some of the more active people ported our
> existing patches to that, and we kept on going.  Again, patches were
> sent back.  When Jolitz released 0.2, again with no patches from the
> Internet community included, it was decided to part ways, and start a
> forked project on the 'net.  This became NetBSD.  After a short time, it
> was obvious that there were two camps: one wanted to keep the OS
> multi-platform, while the other felt it was smarter to ditch that in
> favor of maximizing performance and utility on the Intel platform.  The
> latter group became the FreeBSD project.
>

Both NetBSD and FreeBSD emerged from the 'patchkit' efforts that would take
the good accumulated patches from the net to 386BSD and apply them to try
to cobble together some kind of distribution. It was after Jolitz refused
to play ball with other people at all. It's unfortunate he was the one to
bring 386BSD to market from the net2 distribution in many ways, since it
spawned a Diaspora that's been a mixed blessing: A diversity of platforms
has has lead to more experimentation. It's also lead to a bunch of
duplicated effort when that experimentation lead to a system that made it
hard to share.

Of course, Jolitz wasn't the only strong personality in the early days that
had issues working with others, which also contributed to the Net/Free
split, the later Open/Net split and the even later Free/Dragonfly split...

Then again, Linux is no paragon of people working together either...
There's numerous examples where stupid technical things were done because
of personality disputes (exhibit A: systemd, even Linus can't stop it).


> And yes, the stupid lawsuit came at just the right time for the world to
> adopt Linux instead of BSD, but that's the way the cookie crumbles.  The
> BSD community is doing just fine, thank you, and we still have the
> better product, so there!  ;)
>

I'm with you there, even if we have some denominational differences :)

Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180104/c9778a60/attachment.html>


  reply	other threads:[~2018-01-04 17:28 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 13:43 Noel Chiappa
2018-01-03 14:26 ` Clem Cole
2018-01-03 17:28   ` Bakul Shah
2018-01-03 17:46     ` ron minnich
2018-01-03 18:28       ` Bakul Shah
2018-01-03 18:27     ` Clem Cole
2018-01-03 18:39       ` Forrest, Jon
2018-01-03 18:50         ` ron minnich
2018-01-03 19:56       ` Paul Winalski
2018-01-03 20:24       ` Bakul Shah
2018-01-03 23:40       ` Theodore Ts'o
2018-01-04  0:51         ` Larry McVoy
2018-01-04  2:13           ` Bakul Shah
2018-01-04  2:26             ` Larry McVoy
2018-01-04  3:31               ` Bakul Shah
2018-01-04  2:09         ` Arthur Krewat
2018-01-04  3:21           ` Dan Cross
2018-01-04 17:42             ` Arthur Krewat
2018-01-04 11:53         ` Harald Arnesen
2018-01-04 14:03           ` Clem Cole
2018-01-04 15:54             ` Larry McVoy
2018-01-04 16:45             ` Theodore Ts'o
2018-01-04 17:10               ` Andy Kosela
2018-01-04 17:17               ` Larry McVoy
2018-01-04 18:29                 ` Bakul Shah
2018-01-04 18:50                   ` Larry McVoy
2018-01-04 20:52                     ` Warner Losh
2018-01-04 20:56                       ` Bakul Shah
2018-01-04 20:56                   ` Theodore Ts'o
2018-01-04 21:16                     ` Warner Losh
2018-01-04 22:55                       ` Andy Kosela
2018-01-05 14:27                         ` Clem Cole
2018-01-04 21:17                     ` Bakul Shah
2018-01-04 17:20               ` Tom Ivar Helbekkmo
2018-01-04 17:28                 ` Warner Losh [this message]
2018-01-03 17:07 ` Bakul Shah
  -- strict thread matches above, loose matches on Subject: below --
2018-01-03 17:06 Norman Wilson
2018-01-03  7:53 Andy Kosela
2018-01-03 11:57 ` Ron Natalie
2018-01-03 14:22   ` Random832

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=CANCZdfrG-0cmU9A6PDm72uwqcP1wS47e0rVJPotT-LiFVk6Dmg@mail.gmail.com \
    --to=imp@bsdimp.com \
    /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).