The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] OT: critical Intel design flaw
Date: Thu, 4 Jan 2018 09:03:09 -0500	[thread overview]
Message-ID: <CAC20D2OZ4ZvbJSfzZxBWLanfzZgg3XBTiMNVzHK_0yV9tEbmvg@mail.gmail.com> (raw)
In-Reply-To: <c861d001-48b2-92a9-eef9-fd1cf402a15c@skogtun.org>

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

On Thu, Jan 4, 2018 at 6:53 AM, Harald Arnesen <harald at skogtun.org> wrote:

> Didn't Linus say that if there had been an affordable BSD available at
> the time, he wouldn't have started the Linux project?


​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).  The 386BSD sources were available to all BSD
licensees - as CSRG had put them on the ucbvax ftp server (truth is they
were actually available to anyone there knew how to grab it -- the attempt
to keep the ftp address 'secret' was pretty shallow - not quite announced
on net.noise but it certainly was passed hacker to hacker if you went to a
USENIX conference in those days).​  The funny part was that Linus
university was a BSD licensee and could have gotten it (although I've
personally never seen or heard of evidence that they did).

So this was an example of ignorance of something, not true in fact - That
said, Linus solved the problem he had.  More power to him.  Although his
original kernel was a far cry from '386BSD' - but that was the point.
 When the AT&T case came out, hackers like me were worried 386BSD was going
to go away and started to help make Linux more complete.

I should (as Larry has pointed out) at the time of Linus original work,
some institutions were far more liberal about source access than others.
So even if Linus has known about Jolitz's work, its not clear he
would/could have had access to it.

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


  reply	other threads:[~2018-01-04 14:03 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 [this message]
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
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=CAC20D2OZ4ZvbJSfzZxBWLanfzZgg3XBTiMNVzHK_0yV9tEbmvg@mail.gmail.com \
    --to=clemc@ccc.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).