linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Sipek <jeffpc@optonline.net>
To: Gabor MICSKO <gmicsko@szintezis.hu>, linux-kernel@vger.kernel.org
Subject: Re: SCO offers UnixWare licenses for Linux
Date: Mon, 21 Jul 2003 13:53:17 -0400	[thread overview]
Message-ID: <200307211353.27015.jeffpc@optonline.net> (raw)
In-Reply-To: <1058807414.513.4.camel@sunshine>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 21 July 2003 13:10, Gabor MICSKO wrote:
> http://lwn.net/Articles/40526/
>
> interesting.

"SCO has announced its latest move: concerned Linux users will be able to buy 
a UnixWare License for a "run-time, binary use of Linux." If you buy into 
their protection scheme, they promise not to sue - but only for binary use. 
Looking at the source (or modifying it), it seems, will not be allowed. It 
will be interesting to see how many companies actually buy these licenses."

Sounds like extortion to me..

Jeff.

- -- 
The obvious mathematical breakthrough would be development of an easy
way to factor large prime numbers.
		- Bill Gates, The Road Ahead, pg. 265
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/HCiSwFP0+seVj/4RAjDoAJwMe6Otc1q6EZVUIWqvgs4LyeeMagCfQ4U6
kUhdRCF2gMbCP4IiLOZ0BcA=
=Rk7p
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2003-07-21 17:41 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
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 [this message]
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=200307211353.27015.jeffpc@optonline.net \
    --to=jeffpc@optonline.net \
    --cc=gmicsko@szintezis.hu \
    --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).