The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tytso@mit.edu (Theodore Ts'o)
Subject: [TUHS] Why BSD didn't catch on more, and Linux did
Date: Wed, 7 Feb 2018 14:49:57 -0500	[thread overview]
Message-ID: <20180207194957.GE29650@thunk.org> (raw)
In-Reply-To: <CAC20D2Mk-k8d7Q8+V3N3Dk3+cm1pvazZrmKkATaaCxs5445xwA@mail.gmail.com>

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

On Wed, Feb 07, 2018 at 12:27:34PM -0500, Clem Cole wrote:
> I fear, you are ​falling into an error of thinking about UNIX as the *source cod*
> *​e from Murray Hill* as opposed the* intellectual property *->* i.e.* an
> *implementation* *vs,* *the ideas* of how to build the a computing system.

So what exactly were they claiming?  An interface copyright on
open(2), creat(2), etc.?  Were they they trying to claim that the
concept of an inode was at trade secret?  How the Bourne Shell worked?
How to implement a virtual memory subsystem?

The very first version of POSIX 1003.1 was released in 1988.  This is
four years befure the AT&T lawsuit.  So between the ideas found in
say, Multics, and those things which were promulgated in an
international standard --- which included AT&T representatives ---
exactly what would be covered under Trade Secret law?

> ​  It is these two acts together that the court said, meant that AT&T could
> not longer claim trade secret - they licensed it AND they told people about
> it.

That's basic Trade Secret law.  That's *not* a new and novel law that
the court was promulgating.  It's a basic legal principle taught to
undergraduates --- at least those who take "IT Law for Managers"
offered by the MIT Sloan School :-).  (I always tell students that I
am mentoring that you they should strongly consider taking a basic
legal class and learn enough about accounting to read a balance sheet
and income statement).

More to the point, Trade Secret works differently from Copyright or
Patent.  If Alice reveals to Bob a trade secret under an NDA, and Bob
reveals it to the world, Alice can sue *Bob* for gazillions.  But if
Bob publishes the trade secret in a Usenix ATC paper, and Charlie
learns about it from said Usenix ATC paper, and there is no NDA
between Alice and Charlie --- Alice does *not* have the power to sue
Charlie regarding the trade secret.

Hence, the concept of "AT&T mentally contaminating the world" is
simply not how Trade Secret law works.  And that is a reason why the
wise I/T manager might have to trade off using Trade Secret (where
protection lasts as long as you can keep it a sekrit) versus Patent
(where the protection survives even after it is publically disclosed
--- and you do have to disclose it --- but the protection is
time-limited).

						- Ted


  parent reply	other threads:[~2018-02-07 19:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06 22:13 Dan Stromberg
2018-02-06 22:38 ` Clem Cole
2018-02-06 22:44 ` Warner Losh
2018-02-06 22:59   ` Pete Wright
2018-02-06 22:59 ` Derek Fawcus
2018-02-07  1:14   ` Dave Horsfall
2018-02-06 23:02 ` Theodore Ts'o
2018-02-07  0:22   ` Andy Kosela
2018-02-07  1:02     ` Robert Brockway
2018-02-07  3:47       ` George Michaelson
2018-02-07  1:29   ` Clem Cole
2018-02-07 15:13     ` Theodore Ts'o
2018-02-07 16:59       ` Jon Forrest
2018-02-07 17:27       ` Clem Cole
2018-02-07 19:21         ` Dan Cross
2018-02-07 21:24           ` Clem Cole
2018-02-07 19:31         ` Nemo
2018-02-07 19:49         ` Theodore Ts'o [this message]
2018-02-07 19:53           ` Dan Cross
2018-02-07 20:26             ` Theodore Ts'o
2018-02-07 21:06               ` Clem Cole
2018-02-07 21:31               ` Clem Cole
2018-02-07 17:52       ` Tom Ivar Helbekkmo
2018-02-07  8:04   ` Tom Ivar Helbekkmo
2018-02-07  8:51   ` Arrigo Triulzi
2018-02-07  8:27 ` Wesley Parish
2018-02-07  8:39   ` emanuel stiebler
2018-02-07 10:44     ` Arrigo Triulzi
2018-02-07 13:14   ` Chet Ramey
2018-02-07 14:42   ` Nemo
2018-02-09  2:53     ` Wesley Parish
2018-02-11 20:22       ` Derek Fawcus
2018-02-12  0:31         ` Robert Brockway

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=20180207194957.GE29650@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).