Slashdot Mirror
SCO Claims Kernel Contains UnixWare Code
ergo98 writes "SCO has increased the intensity of the lawsuit with IBM by claiming to hold indisputable proof that copyrighted UnixWare code found its way into Linux, violating the rules of both camps. Whether this is true or not remains to be seen: SCO refuses to divulge the code in question, however they promise to reveal it in court shortly."
about the Sco vs. IBM suit, I can't help but think that SCO is going to be worse off than Mike Tyson's cellmate when all is said and done.
There are four boxes used in defense of liberty: soap, ballot, jury, ammo. Use in that order.
And they are repeated many many times! /*
*/
Those lines are exact duplicates of orginal Unix code! Oh no! They've got us!
Slashdot is like Playboy: I read it for the articles
[*] SCO lawsuit support (EXPERIMENTAL) (NEW)
If Y is selected, then copywrited code from unixware will be compiled into the kernel, if you have millions of $CURRENCY and would like to get SCO after you then say Y, most people would say N here.
Patch here
SCO's up against the wall first!
As someone who bought both Caldera 2.2 and 2.3 when they first came out, I feel I somehow contributed to this mess. So that I might make amends for my actions, unwitting though they were at the time, please allow me to state that:
FUCK SCO AND THE HORSE THEY RODE IN ON.
"The Linux community would have me publish it now, (so they can have it) laundered by the time we can get to a court hearing. That's not the way we're going to go."
Infidels!
So worst case, IBM DID do this (which I doubt), Linux suffers and BSD takes over!?!? Grreeeeeaaat, then we'll have to listen to a bunch of "Linux is dead" trolls. When will it end??? Either way, one thing is for certian:
SCO is dead.
Computer Science is Applied Philosophy
SCO is claiming they have found weapons of mass
destruction in the linux kernel code. The UN will
be assembling an inspection team shortly.
For every annoying gentoo user, are three even more annoying anti-gentoo crybabies. Take Yosh from #Gimp for example.
I bet this is the stolen code:
for (i=0; i<256; i++) {
Dirty, stinking thieves!
So, SCO's taking lessons from the Bush junta, eh?
"We have indisputable proof of their guilt! We are right, we have always been right! Details? Uh... we'll let you know later, we promise. Pinky swear."
Let's set up a fund to collect money from open source users to use for the sole purpose of buying SCO stock. We'll collect enough to just buy the damn company release all IP into the GPL that we own.
And that as they say will be that.
Shop smart, Shop S-Mart.
Even if this is true, shouldn't they have contacted Linus and had him remove the offending code? I'm sure he would have.
Or more to the point-- by distributing the offending products, they are consenting to grant rights to all of the code in question that is in any kernel that they distribute! So really only 2.5.x is vulnerable.
Basically SCO here has failed to adequately protect *anything* and one wonders whether the evidence is falsified. Or maybe the lines of code stolen are probably limited to:
#include
#include
#include
#include
LedgerSMB: Open source Accounting/ERP
/* Drunk. Fix later. (Dennis R) */
"I used to have the two letters posted outside my cube at a previous place of employment. I just tried to find them using Google, but I must not be using the right search terms. "
I don't think Google works THAT well.
You say things that offend me and I can deal with it. Can you?
I have a dollar.
Hang on to that. In a few months, that may be all the money we need...
The search for smoking code has failed. Now is the time to withdraw the inspectors and use force...
Somewhere, something incredible is waiting to be known. -- Carl Sagan
Colin Powell will be presenting the evidence at the UN next month.