From: Stephen Samuel <samuel@bcgreen.com>
To: "James Miller (office)" <jamtat@mailsnare.net>
Cc: linux-newbie <linux-newbie@vger.kernel.org>
Subject: Re: SCO suit and Linux kernel
Date: Sun, 22 Jun 2003 09:33:22 -0700 [thread overview]
Message-ID: <3EF5DA52.4060207@bcgreen.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0306181221130.312@veclin.office>
First of all IANAL (I Am Not A Lawyer) I just like to dabble
in legal issues from time to time.
It's really not clear exactly what SCO is complaining about with
Linux. I'm among those who believe that if the Linux community
could get together, there is good cause for us to put together what
may be the first class-action libel suit. This would be true even
if SCO does have a claim, because they've been both overreaching
in their claims and wilfully vague about their complaint.
Once SCO'x impugned pieces of code are identified and verified as
really belonging to SCO (if that's true!) I would expect that the
Linux community would simply yank out the old code and replace it
with something different.
As a worst case, this legal quagmire that SCO
is trying to create for Linux might stall distribution of 'dirty'
Linux kernels/programs until 'clean' code can be generated. as a
best case, we may end up counter-suing SCO into the ground for
slandering the community (or both!).
Right now, SCO's claim seems to be an inductive one... They're
basically claim that they own and control the rights to any
source that any UNIX licencee has ever put into any copy of
Unix. They're not suing IBM over code that was written by
SCO and/or IBM. They're (currently) suing them over code that
was written by IBM, and/or Coherent (a company that IBM ate).
The claim is a big legal stretch. It's a very strict call on
a small bit of the license... Not only that, but some people
claim that being that pendantic about that piece of code^H^H^H^H
contract would also result in a determination that SCO would
not inherit that right when the UNIX license was transferred
and re-transferred over the last decade.
I have a letter at http://www.bcgreen.com/txt/letters/sco-viral.html
James Miller (office) wrote:
> This may seem a bit off topic for this list, but for me, as a newbie, it
> does involve understanding some things about Linux. I hope it doesn't
> cause any flame wars or anything. Anyway: I understand that SCO's claims
> concern only the 2.4.x kernel and later (i.e., the 2.5.x and thus upcoming
> 2.6 as well). I just don't quite understand how this represents such a
> threat to Linux: Linux already has solid, working kernels in the 2.0.x
--
Stephen Samuel +1(604)876-0426 samuel@bcgreen.com
http://www.bcgreen.com/~samuel/
Powerful committed communication. Transformation touching
the jewel within each person and bring it to life.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2003-06-22 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 17:39 SCO suit and Linux kernel James Miller (office)
2003-06-22 16:33 ` Stephen Samuel [this message]
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=3EF5DA52.4060207@bcgreen.com \
--to=samuel@bcgreen.com \
--cc=jamtat@mailsnare.net \
--cc=linux-newbie@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