The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] Why Linux not another PC/UNIX [was Mach for i386 ...]
Date: Wed, 22 Feb 2017 10:24:40 -0800	[thread overview]
Message-ID: <20170222182440.GE9439@mcvoy.com> (raw)
In-Reply-To: <CAC20D2N74KiRfBzmiGmvyHTgaaMQfPd9QBYc_iUt6nCz7wdA3A@mail.gmail.com>

On Wed, Feb 22, 2017 at 12:00:59PM -0500, Clem Cole wrote:
> > A lot of us were pretty sick of that legal bullshit.
> >
> ???Actually - that was exactly the point.   A lot of folks did not think that
> the AT&T copyright mattered any more.  I think most of us at the time we
> sick of it.     The code base had been rewritten.  

Sorry to keep yapping on this, but I think we're trying to get at accurate
history, right?

So what is written there was not how I felt at all.  I personally felt
like AT&T had a case, I thought it was copyright not trade secret.  I went
through the code, I had access to the AT&T code and the free code.  I was
a UFS/FFS hacker at the time so that's what I read.  I found routines
that were bit for bit identical in both in less than 5 minutes.  The one
I remember was bmap(), I found a couple of others that I don't remember
(just remember there were more) and I gave up in disgust.  I was pretty
disappointed that CSRG considered this not AT&T source, it was.

That left me with a strong feeling that AT&T was going to win.  I was
wrong but it didn't matter, BSD was sort of dead to me.  I can't tell
you how painful that was for me, I was very much a BSD guy, SunOS was
BSD plus the stuff you would want fixed, fixed.

Linux wasn't BSD but it wasn't going to get taken away from me like
SunOS was taken away and now BSD looked like it was going to be taken
away.  It just looked like a bad investment to work on BSD so I worked
on Linux.


  parent reply	other threads:[~2017-02-22 18:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22  3:38 Clem Cole
2017-02-22  4:28 ` Dan Cross
2017-02-22 15:36   ` Clem Cole
2017-02-22 16:11     ` Larry McVoy
2017-02-22 17:00       ` Clem Cole
2017-02-22 17:06         ` Chet Ramey
2017-02-22 18:24         ` Larry McVoy [this message]
2017-02-22 19:35           ` Clem Cole
2017-02-22 20:18             ` arnold
2017-02-22 22:11               ` Clem Cole
2017-02-22 21:34             ` Larry McVoy
2017-02-22 22:56               ` Clem Cole
2017-02-22 23:13                 ` Larry McVoy
2017-02-22 23:51                   ` Clem Cole
2017-02-22 23:51           ` Paul Ruizendaal
2017-02-23 19:15             ` Clem Cole
2017-02-23 20:31               ` Random832
2017-02-23 22:48                 ` Joerg Schilling
2017-02-24  2:07                   ` Jason Stevens
2017-02-23 23:06                 ` Wesley Parish
2017-02-22 17:41       ` Arthur Krewat
2017-02-22 21:00     ` Michael Kerpan
2017-02-22 22:03       ` Arno Griffioen
2017-02-22 22:51         ` Larry McVoy
2017-02-22 23:29         ` Clem Cole
2017-02-23  4:53           ` Gregg Levine
2017-02-22 22:18       ` Clem Cole
2017-02-24  3:53     ` Dan Cross
2017-02-22  5:56 ` Steve Nickolas
2017-02-24  5:31   ` John Labovitz

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=20170222182440.GE9439@mcvoy.com \
    --to=lm@mcvoy.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).