SCO Cleared Official Linux Kernel of Tainted Code
In a previous story looking into SCO-Caldera's vague and naked claims that there is SCO-owned code in Linux, we reported that Chris Sontag said SCO had not found SCO-owned code in the kernel.org Linux kernel.
The discussion went like this:
Since that article was published, SCO-Caldera has returned to its prior posture of trying again to vaguely implicate the kernel.org Linux kernel. However, we believe at this time that SCO-Caldera is blowing smoke again -- as part of its war on the entire Linux community. That topic is discussed some here today and will be discussed further in some upcoming MozillaQuest Magazine articles.
SCO Wants to Hurt Linux Development and Deployment
Up to that discussion with Chris Sontag, as far as we know, SCO spokespeople had refused to be specific as to what they were alluding with their accusations that there is SCO-owned code in Linux. Moreover, SCO-Caldera either has been unable to, or unwilling to, point to specific SCO-owned code in what it loosely calls Linux.
Many people in the Linux community believe this is an intentional SCO-Caldera strategy aimed at disrupting Linux kernel, GNU/Linux operating system, and Linux software development. Linux community members also believe that SCO-Caldera's strategy is to stifle Linux distribution and Linux software sales, marketing, and deployment.
IBM states that belief in the preamble to its Answer to SCO-Caldera's lawsuit: . . . contrary to Caldera's allegations, by its lawsuit, Caldera seeks to hold up the open source community (and development of Linux in particular) by improperly seeking to assert proprietary rights over important, widely used technology and impeding the use of that technology by the open source community.
If there is SCO-owned code in the core kernel.org Linux kernel, then that tainted Linux kernel code likely would be in every Linux distribution and every Linux-based computer system. This is a particularly key issue not only for the Caldera v IBM lawsuit, but also for SCO-Caldera's ability to attack just about every Linux distribution provider (LDP) and perhaps every Linux-based operating system user.
Of course whether SCO-Caldera could prevail in such copyright infringement claims is an entirely different matter. We examine that question in an upcoming MozillaQuest Magazine article.
SCO Has Not Shown Any SCO-code in Linux Kernel or GNU/Linux OS
Some two months ago, in our 18 March 2003 article, Alan Cox, Richard Gooch, and David Weinehall Respond to SCO's Linux-Related Claims, we noted that so far SCO had not publicly identified any SCO-owned code residing anyplace in Linux and challenged SCO-Caldera CEO, Darl McBride, to show publicly any such code:
SCO-Caldera's CEO Darl McBride and associates, have failed to offer proof that the Linux kernel and GNU/Linux are derived from SCO-owned Unix source code. Can you, Darl McBride, forthwith and without delay show substantial amounts of Linux kernel and/or GNU/Linux source code are the same as SCO-owned source code? Can you show us any Linux kernel and/or GNU/Linux source code are the same as SCO-owned source code?
Do you, Darl McBride, have articulable proof that Caldera-owned proprietary knowledges, skills, and methodologies were used in Linux kernel and/or GNU/Linux operating system development? If so, what is that proof -- other than a bald assertion?
So far Darl McBride, you have failed to offer any proof of your naked claims! Please, Darl McBride, show us your proof so that we all can see it.
That's still the case. So far Darl McBride, has failed to offer any proof of his naked claims!
Please see the first two parts of our series about SCO-Caldera's IP claims plus its intentions to enforce and license its intellectual property rights.
Related MozillaQuest Articles
SCO-Caldera v IBM: