All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Downing, Thomas" <Thomas.Downing@ipc.com>
To: "'Sancar Saran'" <saran@sim.com.tr>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: RE: SCO offers UnixWare licenses for Linux
Date: Fri, 25 Jul 2003 09:37:05 -0400	[thread overview]
Message-ID: <170EBA504C3AD511A3FE00508BB89A920234CD5E@exnanycmbx4.ipc.com> (raw)

> -----Original Message-----
> From: Sancar Saran [mailto:saran@sim.com.tr]
> Sent: Friday, July 25, 2003 7:44 AM

> > #1 The whole thing is without merit (as it seems to be now)
> > #2 IBM did it and have to buy SCO (because everyone will 
> sue IBM, every
> > Linux developer, every business, every user)
> > #3 SCO gets bankrupted by countersuits (popular US approach to law)
> >
> 
> It look like good plan, and my question is not answered. Are 
> distro makers  
> safe in these time line? What if Red Hat goes bankrupt before the SCO 
> falldown.
> 

I hope someone does take action, SCO vs. IBM doesn't come to trial
till April 11, 2005.  A lot of damage could be done in that time,
assuming some other event (like an acquisition) doesn't obviate
the whole mess.

To date, the only thing I've seen is:
www.theregister.co.uk/content/61/31910.html

             reply	other threads:[~2003-07-25 13:22 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25 13:37 Downing, Thomas [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
     [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-22 23:34 Clayton Weaver
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=170EBA504C3AD511A3FE00508BB89A920234CD5E@exnanycmbx4.ipc.com \
    --to=thomas.downing@ipc.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saran@sim.com.tr \
    /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.