All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Diego Calleja García" <diegocg@teleline.es>
Cc: Michael Bernstein <michael@seven-angels.net>,
	gmicsko@szintezis.hu, linux-kernel@vger.kernel.org
Subject: Re: SCO offers UnixWare licenses for Linux
Date: Mon, 21 Jul 2003 16:09:43 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0307211518420.421@chaos> (raw)
In-Reply-To: <20030721205940.7190f845.diegocg@teleline.es>

On Mon, 21 Jul 2003, Diego Calleja [ISO-8859-15] García wrote:

> El Mon, 21 Jul 2003 13:52:21 -0400 Michael Bernstein <michael@seven-angels.net> escribió:
>
> > To put it simply, just because they "may,"  - and I say may here simply
> > because we have no evidence to prove their claims but cannot flatly
> > deny them - own the rights to Sys V, does NOT mean they own the right
>
> So they want to sell us something that still hasn't proved....cool.
>

No. They want to sell you something you already own. SCO is the
owner of a non-exclusive license to a 30 year-old operating
system. There are many others who have such a license including
the University of California in Berkeley. Much of Linux was designed
to interface with the API that they published, in a method that
minimizes the changes to a 'C' runtime library. This made porting
of various Unix utilities developed by the students at Berkeley,
relatively easy.  The actual Unix API used by Berkeley, was published
by AT&T in December 1983. It is Called "Unix System V, Release 2.0,
User Reference Manual Including BTL Computer Center Standard and
Local Commands". I have a copy of that two volume ring-bound book.

A "non-exclusive license" means that you you are not the only
person who has been licensed. It's just that simple. In my opinion
there is no way that SCO will ever convince any court that their version
of "non-exclusive" is any different than all the others including,
but not limited to, BSD, Digital, Interactive, Sun, IBM, Microsoft,
Novell, etc. I have read the complaint and they allege that somebody
must have stolen their secrets because nobody could make a version
of Unix good enough for "the enterprise" without their secrets.
So, they contend that they are the only people smart enough to write
software for "the enterprise", whatever that is. Nice trick.

Note that in the complaint against IBM, SCO seeks a jury trial.
I guess they think it's easier to snow a jury than a judge. We'll
see. I think SCO thinks juries are stupid and will treat them
as David and Goliath. I think a jury will treat them like
thieves, instead.

It is instructive to read the annual reports, filed with the
United States Security and Exchange Commission, by many
of the companies that produce software. These reports are
available on the "Web" and the various company's Web Pages
usually have links to recent filings. A quote from a portion
of Novel's 2002 Annual report goes like this; " The software
industry is characterized by frequent litigation regarding
copyright, patent, and other intellectual property rights."

The fact that somebody sues somebody else in the Software
Industry is kind of like having the sun rise in the East.
You get to expect it. Now, back to writing some software
that somebody may claim I stole.............


Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.


  reply	other threads:[~2003-07-21 19:54 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-21 17:10 SCO offers UnixWare licenses for Linux 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 [this message]
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
2003-07-21 17:24 Mudama, Eric
2003-07-22 23:34 Clayton Weaver
     [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-25 13:37 Downing, Thomas
2003-07-26  8:21 Anuradha Ratnaweera
2003-07-26 14:49 ` Henrik Persson

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=Pine.LNX.4.53.0307211518420.421@chaos \
    --to=root@chaos.analogic.com \
    --cc=diegocg@teleline.es \
    --cc=gmicsko@szintezis.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@seven-angels.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.