linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sancar Saran <saran@sim.com.tr>
To: Larry McVoy <lm@bitmover.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SCO offers UnixWare licenses for Linux
Date: Thu, 24 Jul 2003 18:49:07 +0300	[thread overview]
Message-ID: <200307241849.07827.saran@sim.com.tr> (raw)
In-Reply-To: <20030724150841.GA12647@work.bitmover.com>

Hi,

On Thursday 24 July 2003 18:08, Larry McVoy wrote:
> On Thu, Jul 24, 2003 at 04:52:09PM +0200, Felipe Alfaro Solana wrote:
> > On Mon, 2003-07-21 at 20:59, Diego Calleja 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.
> >
> > And can be rewritten from scratch if necessary... They're crazy!
>
> There seems to be a prevailing opinion that if there is stolen code in
> Linux that came from SCO owned code that all that needs to be done is
> to remove it and everything is fine.  I don't think it works that way.
> If code was stolen and the fact that it is in Linux helped destroy
> SCO's business then SCO has the right to try and get damages.  I.e.,
> Linux damaged SCO by using the code.
>
> It's also not a simple case of rewriting.  _Assuming_ that there was
> something significant in Linux which came from SCO, i.e., they can make
> the case that the Linux community wouldn't have thought of it on their
> own, then you don't get to rewrite it because now you know how whatever
> "it" is works and you didn't before.
>
> The business world takes their IP seriously.  If, and it is a big if,
> there is code in Linux from SCO, that's going to be a nasty mess to
> clean up and we had better all pray that IBM just buys them and puts
> Unix into the public domain.  Otherwise I think SCO could force Linux
> backwards to whereever it was before the tainted code came in.  If that
> happens, I (and I suspect a lot of you) will work to make sure that
> things which couldn't possibly be tainted (like drivers) do make it
> forward.
>
> If SCO prevails it won't be the end of the world.  A lot of that
> scalability stuff is just a waste of time, IMO.  32 processor systems are
> dinosaurs that are going away and I'm not the only one who thinks so, Dell
> and IDC agree:
>
> 	http://news.com.com/2100-1010_3-1027556.html
>
> Don't get me wrong, there are some cool things in 2.5 that we all want but
> if SCO puts a dent in the works Linux will recover and maybe be better.

I wish to know are we have backup plan any backup plan. Most of Linux users 
are gonna worry. 

Today I get a e mail from our local mailing lists. Says SCO sued Red Hat for 
this. another one asks Can M$ send BSA to check their systems and request 
licence money (because of buying SCO Unixware Licences). 

Rumors everywhere, people can't track of all sources about SCO vs IBM(Linux) 
case and each Rumor hurt us too badly. Every news people are gonna make worst 
case scenario and this is preventing people to buy expensive linux server 
systems (like rhas etc).

Of course Linux will live. I haven't got any question about it. But I fear 
this case between SCO and IBM may hit Red Hat, Suse and others. I believe non 
of these distros are disposable (uh oh expect Caldera/SCO).

Is there any way for backup plan?

I believe the backup plan will shut up SCO and burn those plans forever. 

Waiting for IBM is not good idea. 

Ps: I home my enlish enough to tell what I mean.. :)

Sancar "Delifisek" Saran



  reply	other threads:[~2003-07-24 15:34 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 [this message]
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=200307241849.07827.saran@sim.com.tr \
    --to=saran@sim.com.tr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    /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).