From: cym224@gmail.com (Nemo)
Subject: [TUHS] Why BSD didn't catch on more, and Linux did
Date: Wed, 7 Feb 2018 14:31:21 -0500 [thread overview]
Message-ID: <CAJfiPzy03j=YKtppxxukCWv43XmiP_yCiftgUdToDF9zH9jDkg@mail.gmail.com> (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: 810 bytes --]
On 07/02/2018, Clem Cole <clemc at ccc.com> wrote (in part):
> As a minor footnote, I've always wonder about the SCO case being anything
> but a delay tactic against Linux. Give the courts results from the AT&T
> vs. BSDi case, I'm personally surprised they got as far as they did. I
> really would expected to be tossed out at the start (hut Im not a lawyer of
> course). Clearly, the courts had declared that ideas were free and clear
> for anyone to use. So how SCO could have claimed anything against anyone,
> I find hard to fathom. Again the courts got it right, but it took a loot of time
> and effort for then to decide something that the another court had already decided.
The entire painful journey can be read on Groklaw and well worth
reading when you have a spare month or so.
N.
next prev parent reply other threads:[~2018-02-07 19: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 [this message]
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
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='CAJfiPzy03j=YKtppxxukCWv43XmiP_yCiftgUdToDF9zH9jDkg@mail.gmail.com' \
--to=cym224@gmail.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).