The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tytso@mit.edu (Theodore Ts'o)
Subject: [TUHS] OT: critical Intel design flaw
Date: Thu, 4 Jan 2018 11:45:57 -0500	[thread overview]
Message-ID: <20180104164557.GI23371@thunk.org> (raw)
In-Reply-To: <CAC20D2OZ4ZvbJSfzZxBWLanfzZgg3XBTiMNVzHK_0yV9tEbmvg@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]

On Thu, Jan 04, 2018 at 09:03:09AM -0500, Clem Cole wrote:
> ​You need to add >>and that he knew about and had access<<.
> 
> The truth is there was and it had networking and X windows already.  Bill
> Jolitz had completed the original 386 BSD port (and actually started to
> publish about it in DDJ).

How real was it in June 1991, when he demo'ed it in Usenix Anaheim?
Was it at the level of a "MIT Media Lab demo", or was it actually
something that could be used in anger?

The official history states that 386 BSD version 0.0 was released in
March 1992, and the "much more usable" 0.1 version was released in
July 1992.

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.

Contrast that to Linus, where I started playing with Linux in
September 1991 (Linux 0.09), and in three months he accepted fairly
major patches from me to implement all of the new syscalls and changes
needed to implement POSIX Job Control and POSIX termios (Linux 0.12).
The Linux developers were not spending time fighting over who would
get commit bits; we were having fun writing code.

						- Ted


  parent reply	other threads:[~2018-01-04 16:45 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 [this message]
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
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=20180104164557.GI23371@thunk.org \
    --to=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).