linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Clayton Weaver" <cgweav@email.com>
To: linux-kernel@vger.kernel.org
Subject: re: SCO offers UnixWare licenses for Linux
Date: Tue, 22 Jul 2003 18:34:34 -0500	[thread overview]
Message-ID: <20030722233435.25143.qmail@email.com> (raw)

(Pardon me if this reiterates information already
posted in this thread. From the few messages I
browsed, it seems like people do not generally
know this.)

SCO only owns the Unixware source code. They do
not own any earlier copyrights on SVR4 unix
(on which SCO's claims of infringement of
intellectual property rights are based)
that were purchased  by Novell from AT&T,
because Novell did not include those copyrights
in the terms of their sale of Unixware to SCO.

Novell's statement of position on the case:

<http://www.novell.com/news/press/archive/2003/05/pr03033.html>

[Note: my previous claim in private to a couple of posters that the property rights in question were made public domain by AT&T as part of an earlier antitrust settlement were not accurate. When Unix was invented, AT&T was forbidden by a US antitrust settlement in the 1950s from vending anything
other than telco services. So they gave the unix source of the day away for no more than the cost of copying it and sending it to someone that wanted it. This restriction on what markets AT&T could market to was eased by a revision
of the antitrust settlement in the early 1980s, which removed several regional telephone companies from AT&T ownership and gave AT&T the right to sell ancillary products like software. AT&T always held the copyrights on System V unix, because
their employees wrote it, but up until about 20 years ago they couldn't sell them or charge for licensing.]

Still, there is the question of whether any such claims of intellectual property rights on the design (rather than a specific implementation)
of unix are valid. How much did the unix api borrow from earlier user interfaces designed
under the auspices of a variety of different computer software companies (and perhaps even under US government contract, which would probably make the copyrights prior art owned by the American public, given the terms of US
government software development contracts in the '60s and '70s)? This question about the origins
of the unix api has never been examined in court.

["Look and feel" copying is ambiguous in US
legal precedent. The Lotus 1-2-3 case was decided in favor of the original designers, while the Apple-Microsoft case was decided in favor of
the reimplementer-using-different-source-code.]

Anyway, the upshot is that Novell could possibly make the case that SCO is trying to make if they were sufficiently motivated, believed that AT&T had copied nothing in the unix API from earlier prior art not owned by AT&T, and believed that a court would decide that other unix-like
operating systems infringe their copyrights.
But SCO themselves never bought the property rights from Novell that they claim as the basis
for the current campaign of fud.

(Looks to me like nothing more than some lawyers bilking the SCO and IBM stockholders and anyone
else that they can suck into the litigation
on a case with no valid basid in any property
owned by SCO.)

Regards,

Clayton Weaver
<mailto: cgweav@email.com>

-- 
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

CareerBuilder.com has over 400,000 jobs. Be smarter about your job search
http://corp.mail.com/careers


             reply	other threads:[~2003-07-22 23:19 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22 23:34 Clayton Weaver [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-26  8:21 SCO offers UnixWare licenses for Linux Anuradha Ratnaweera
2003-07-26 14:49 ` Henrik Persson
2003-07-25 13:37 Downing, Thomas
     [not found] <20030724234213.GA20064@work.bitmover.com>
2003-07-25  0:11 ` Michael Bernstein
2003-07-25  0:21   ` Larry McVoy
2003-07-25 12:43     ` Jamie Lokier
2003-07-25 13:37       ` David S. Miller
2003-07-25 15:09         ` Yaroslav Rastrigin
2003-07-25 15:10           ` David S. Miller
2003-07-25 15:17           ` Larry McVoy
2003-07-21 17:24 Mudama, Eric
2003-07-21 17:10 Gabor MICSKO
2003-07-21 17:52 ` Michael Bernstein
2003-07-21 18:59   ` Diego Calleja García
2003-07-21 20:09     ` Richard B. Johnson
2003-07-21 20:36       ` Shawn
2003-07-24 14:52     ` Felipe Alfaro Solana
2003-07-24 15:08       ` Larry McVoy
2003-07-24 15:49         ` Sancar Saran
2003-07-24 19:32           ` Alan Cox
2003-07-25 11:44             ` Sancar Saran
2003-07-24 15:54         ` Richard B. Johnson
2003-07-24 16:01           ` Larry McVoy
2003-07-24 16:17             ` Tomas Szepe
2003-07-24 16:39             ` Yuliy Pisetsky
2003-07-24 16:55               ` Larry McVoy
2003-07-24 18:48                 ` nick
2003-07-24 16:52             ` Ian Hastie
2003-07-24 17:22               ` Larry McVoy
2003-07-24 22:52                 ` Stephan von Krawczynski
2003-07-24 17:00             ` David Benfell
2003-07-24 17:34         ` Felipe Alfaro Solana
2003-07-24 17:46           ` Shawn
2003-07-24 22:55           ` Jan Harkes
2003-07-24 23:27           ` Stephan von Krawczynski
2003-07-25 19:29           ` Timothy Miller
2003-07-24 21:03         ` Leandro Guimarães Faria Corsetti Dutra
2003-07-21 17:53 ` Jeff Sipek
2003-07-21 22:35   ` Brian McGroarty
2003-07-22 19:48     ` Jamie Lokier
2003-07-22  3:41 ` Kurt Wall

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=20030722233435.25143.qmail@email.com \
    --to=cgweav@email.com \
    --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;
as well as URLs for NNTP newsgroup(s).