From: Raimundo Bilbao <rbilbao@inzignia.cl>
To: "Lauro, John" <jlauro@umflint.edu>, <linux-kernel@vger.kernel.org>
Subject: Re: SCO's claims seem empty
Date: Mon, 2 Jun 2003 23:02:21 -0400 [thread overview]
Message-ID: <200306022302.21976.rbilbao@inzignia.cl> (raw)
In-Reply-To: <37885B2630DF0C4CA95EFB47B30985FB0187FFE7@exchange-1.umflint.edu>
El Lun 02 Jun 2003 22:18, Lauro, John escribió:
> From what I read when SCO had more on their web site, it's more a
> question of contract violation. IBM had a contract for their Unix, and
> developed their code for that. Then IBM ported some of their "own"
> kernel mods that was written for AIX and released it into Linux for
> free. That violated some portion of the Unix contract. Thus, if IBM
> wins, could have implications against some parts of GPL, and maybe
> that is why Microsoft is backing SCO.
>
> I may be way off base, but SCO always stated it was contract issues
> and not code or copyright.
[...]
Ok, but all this noise (AFAIK) was started from a sue against IBM not Linux,
however (pretty) soon was focused on some _mitical_ portions of the linux
kernel (I really want to read those ET codes, maybe I can learn alot from
those aliens's gurues ;-D) and then toward GNU licenses and some others
wired implications.
I really think SCO haven't a real case against Linux (maybe toward IBM, but
not linux), however everybody knows what a _special_ group of lawyers can do,
no? ;-)
Another think what ringing on mi (little) brain is the simple question :
somebody remember the surprise off know, sometime ago, that NT was include
zlib's code into this?, now I asking myself, what else they have _included_?,
the SCO sue has some implications against them?. Maybe I never know, but it's
an intersting question, maybe SCO (or anybody else) ending with a sue to
every operating system on this planet from now toward if they want (a really
nasty scenario).
OK, enough of this, let's R&R and back to work... ;-D
cheers
mundo
next prev parent reply other threads:[~2003-06-03 2:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 2:18 Lauro, John
2003-06-03 3:02 ` Raimundo Bilbao [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-01 17:35 Downing, Thomas
2003-05-30 8:04 Martin List-Petersen
2003-05-30 13:01 ` Paul Rolland
2003-05-30 20:20 ` Mark Mielke
2003-05-31 23:06 ` brian
2003-06-01 7:56 ` Paul Rolland
2003-06-01 9:22 ` Lionel Elie Mamane
2003-06-01 9:38 ` Markus Plail
2003-06-01 9:59 ` Adrian Bunk
2003-06-01 9:40 ` Riley Williams
2003-06-01 10:00 ` Michael Frank
2003-06-02 0:03 ` Horst von Brand
2003-06-01 9:40 ` Nicolas Vollmar
2003-06-01 9:58 ` Valdis.Kletnieks
2003-06-01 9:55 ` Adrian Bunk
2003-06-01 9:56 ` Michael Frank
2003-06-01 12:34 ` Paul Rolland
2003-06-01 12:52 ` Richard B. Johnson
2003-06-02 0:15 ` Martin List-Petersen
2003-06-02 1:19 ` Horst von Brand
2003-06-02 11:10 ` uaca
2003-06-02 11:24 ` Stefan Smietanowski
2003-06-06 12:31 ` Martin List-Petersen
2003-06-06 15:13 ` Alan Cox
2003-06-06 16:22 ` Paul Rolland
2003-06-06 17:20 ` Richard B. Johnson
2003-06-06 22:17 ` Martin List-Petersen
2003-06-06 22:33 ` Rob Landley
2003-06-12 10:20 ` Martin List-Petersen
2003-06-02 11:39 ` Marcus Metzler
2003-06-03 0:42 ` Raimundo Bilbao
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=200306022302.21976.rbilbao@inzignia.cl \
--to=rbilbao@inzignia.cl \
--cc=jlauro@umflint.edu \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®