DISCLAIMER DISCLAIMER DISCLAIMER DISCLAIMER

Die hier archivierte Mail kann, muss sich aber nicht auf den Themenkomplex von Oekonux beziehen.

Insbesondere kann nicht geschlossen werden, dass die hier geäußerten Inhalte etwas mit dem Projekt Oekonux oder irgendeiner TeilnehmerIn zu tun haben.

DISCLAIMER DISCLAIMER DISCLAIMER DISCLAIMER

Message 00504 [Homepage] [Navigation]
Thread: choxT00504 Message: 1/1 L0 [In date index] [In thread index]
[First in Thread] [Last in Thread] [Date Next] [Date Prev]
[Next in Thread] [Prev in Thread] [Next Thread] [Prev Thread]

[chox] Why SCO will soon be going after BSD



| Why SCO will soon be going after BSD
|
| [...]
|
| SCO is going to attack the 1994 AT&T/BSD settlement. That's a very
| interesting item that the few favored analysts (and only a select few
| journalists) who were allowed to ask questions failed to pick up on.
| Here's our take on why SCO is embarking on this new course of action:
|
| SCO has steadfastly refused to get specific about infringement of its
| IP. That's probably not because they are coy, but rather because they
| can't. The few snippets of code it dared to make public already have
| been laughed off the stage and quite thoroughly debunked. With both IBM
| and Red Hat now demanding in court that SCO show its cards, the company
| came to realization that it was either at the end of the trail or that
| it had to broaden its horizons.
|
| They've chosen the latter. CEO Darl McBride, in fact, used the term
| "broad and deep" several times in his remarks, and that was no accident.
| Since they cannot show infringement of SCO Unix code, SCO now plans to
| challenge the 9-year-old settlement between AT&T and BSD. If it can
| successfully do that, then its claims that Linux contains tainted code
| can be substantiated. If it can't, SCO is dead meat.

[ http://www.newsforge.com/business/03/11/18/1742216.shtml ]

Holger

-- 
PGP fingerprint:  F1F0 9071 8084 A426 DD59  9839 59D3 F3A1 B8B5 D3DE
_______________________
http://www.oekonux.de/



[English translation]
Thread: choxT00504 Message: 1/1 L0 [In date index] [In thread index]
Message 00504 [Homepage] [Navigation]