The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Why BSD didn't catch on more, and Linux did
Date: Wed, 7 Feb 2018 16:31:56 -0500	[thread overview]
Message-ID: <CAC20D2OefkHDHy_z5q957yc3BiePmvF9pDUJPwLvf_xxzg9k9w@mail.gmail.com> (raw)
In-Reply-To: <20180207202654.GF29650@thunk.org>

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

On Wed, Feb 7, 2018 at 3:26 PM, Theodore Ts'o <tytso at mit.edu> wrote:

>
> AT&T's legal argument was against BSDI and UCB.  People
> misunderstanding the difference between Patent law and Trade Secret
> Law into thinking that we were all contaminated and Unix was Doomed
> (tm), wasn't, as far as I know, part of AT&T's lawsuit.
>

Sadly, yes it was so... (and I still have my 'mentally contaminated'
button).​  So now you do know,

Again this is why (and I have asked counsel this question) so what if they
had won?   I have been advised that all UNIX implementations would have
been subjected to the ruling world-wide or at least subject to a number
of treaties enforce in the USA and the EU (although how many AT&T would
have litigated against we will never know).   My friends that are lawyers
that have examined this question have said in practice it would have been
very hard to pursue (which may have been part of the reason the court did
what it did - i.e. the test could this be enforced).

It would have been very different world that I am fairly sure.

Clem
ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180207/c4c437cc/attachment.html>


  parent reply	other threads:[~2018-02-07 21:31 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
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 [this message]
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=CAC20D2OefkHDHy_z5q957yc3BiePmvF9pDUJPwLvf_xxzg9k9w@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).