The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Jason Stevens <jsteve@superglobalmegacorp.com>
Cc: UNIX Heritage Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Early Linux and BSD (was: On the origins of Linux - "an academic question")
Date: Sat, 18 Jan 2020 07:49:48 -0800	[thread overview]
Message-ID: <20200118154948.GE28686@mcvoy.com> (raw)
In-Reply-To: <25E62EB5E090E7CB.0e52e059-5d83-4d31-98f4-bb2d82ede4f8@mail.outlook.com>

On Sat, Jan 18, 2020 at 03:35:40PM +0000, Jason Stevens wrote:
> Internet legend is that the rift was massive.????

It was and Jolitz was unfairly crapped on at a Usenix, the one after
the lawsuit.  At the time, everyone thought it was about copyright and
Jolitz told me that there was a lot of code that was unchanged from v7.
He knew that I knew the file system code and he said "Go look at bmap(),
it's byte for byte exactly the same".  He was right and there was other
stuff, it wasn't just one function.

This was after both BSDI and 386BSD were a thing.  At a Usenix conference,
the BSDI guys pissed all over him, put down his efforts on 386BSD,
it was obviously self serving because they wanted a business, but it
wasn't a nice thing to do at all.

Bill thought he had the goods on them for copyright infringement but
he held his tongue and took the abuse because he didn't want to help
the lawsuit.  In his mind, he was a martyr for the cause.

So, yeah, those guys didn't like each other.  I know all of them and
wished they had handled this better.

I heard about all this, I was probably at that Usenix or maybe someone
told me, I don't remember.  I felt bad for Bill and was in a position
where I could hire him, so I did.  He didn't really do anything for me
though we did have some fascinating discussions about the short comings
of C++ and mused about how a language would have to work to truly layer
"correctly".  The context was the SCSI subsystem, it was part replicated
protocol in each driver and part driver specific stuff and we were trying
to imagine a programming language that would let us have the replicated
stuff in one place and plumb in the specific stuff as needed.  Needless to
say, we didn't come up with an answer but it was a fun thought experiment.
He's a sharp guy, quirky, but sharp.

  reply	other threads:[~2020-01-18 15:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-18 15:35 Jason Stevens
2020-01-18 15:49 ` Larry McVoy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-01-19 16:05 Noel Chiappa
2020-01-19 14:17 Noel Chiappa
2020-01-19 20:49 ` Nemo Nusquam
2020-01-17 16:01 [TUHS] On the origins of Linux - "an academic question" Arrigo Triulzi
2020-01-17 19:59 ` Arno Griffioen
2020-01-18  3:50   ` Theodore Y. Ts'o
2020-01-18  4:19     ` [TUHS] Early Linux and BSD (was: On the origins of Linux - "an academic question") Greg 'groggy' Lehey
2020-01-18 15:25       ` Larry McVoy
2020-01-18 16:19         ` reed
2020-01-19  2:49       ` Theodore Y. Ts'o
2020-01-19  3:12         ` Greg 'groggy' Lehey
2020-01-19  3:58           ` Greg 'groggy' Lehey
2020-01-19 13:25             ` Theodore Y. Ts'o
2020-01-19 13:48               ` Clem Cole
2020-01-20  3:32               ` Greg A. Woods
2020-01-20  3:51                 ` George Michaelson
2020-01-20 17:19                   ` Clem Cole
2020-01-20 17:49                     ` Warner Losh
2020-01-20 19:00                       ` Clem Cole
2020-01-20 18:04                     ` Larry McVoy
2020-01-20 18:09                       ` David Barto
2020-01-20 19:18                       ` Clem Cole
2020-01-20 19:46                         ` Jon Steinhart
2020-01-20 20:15                           ` Clem Cole
2020-01-22  0:14                       ` Greg A. Woods
2020-01-21  0:44                     ` Bakul Shah
2020-01-20 19:09                 ` Theodore Y. Ts'o
2020-01-20 19:51                   ` Clem Cole
2020-01-20 23:04                   ` Greg A. Woods
2020-01-21  0:13                     ` Warner Losh
2020-01-21 23:45                       ` Greg A. Woods

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=20200118154948.GE28686@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=jsteve@superglobalmegacorp.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).