The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pnr@planet.nl (Paul Ruizendaal)
Subject: [TUHS] Why Linux not another PC/UNIX [was Mach for i386 ...]
Date: Thu, 23 Feb 2017 00:51:11 +0100	[thread overview]
Message-ID: <0793B069-8A80-450E-9E49-68C19448C2E9@planet.nl> (raw)
In-Reply-To: <20170222182440.GE9439@mcvoy.com>


On 22 Feb 2017, at 19:24 , Larry McVoy wrote:

> 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'm not a lawyer, but wasn't part of the background that prior to 1988
in US law one could not claim both copyright and trade secret protection,
and that for something to be copyrighted it had to expressly claim to
be copyrighted material, and be registered as such?

I have a vague recollection that the AT&T legal department instructed the
Unix team to remove copyright notices from the Unix source (and this seems
supported by code, see for instance:
http://minnie.tuhs.org/cgi-bin/utree.pl?file=V5/usr/sys/ken/sys1.c
and
http://minnie.tuhs.org/cgi-bin/utree.pl?file=V6/usr/sys/ken/sys1.c)
because the legal folks thought that trade secret was a stronger
protection for software?

I also seem to recall that the AT&T code base included original material
from CSRG where the copyright notice had been removed by USL.

All in all, the USL lawyers probably felt that they would lose the case if
fought on the grounds of copyright violations alone.

I wish something like Groklaw had existed during the USL-UCB case: the
legal twists and turns would have been documented a lot better. There is
some material though, see:
http://www.groklaw.net/staticpages/index.php?page=legal-docs#bsdi
The amicus brief by the Regents, and the settlement make for interesting
reading. If the position taken by the Regents is correct, all of Unix
up to and including 32V is in the public domain now.

Warren: the links from Groklaw to TUHS are broken, perhaps because of
the recent reorganization of the archive.




  parent reply	other threads:[~2017-02-22 23:51 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
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 [this message]
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=0793B069-8A80-450E-9E49-68C19448C2E9@planet.nl \
    --to=pnr@planet.nl \
    /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).