Slashdot Mirror
Claimed Proof That UNIX Code Was Copied Into Linux
walterbyrd writes "SCO's ex-CEO's brother, a lawyer named Kevin McBride, has finally revealed some of the UNIX code that SCO claimed was copied into Linux. Scroll down to the comments where it reads: 'SCO submitted a very material amount of literal copying from UNIX to Linux in the SCO v. IBM case. For example, see the following excerpts from SCO's evidence submission in Dec. 2005 in the SCO v. IBM case:' There are a number of links to PDF files containing UNIX code that SCO claimed was copied into Linux (until they lost the battle by losing ownership of UNIX)." Many of the snippets I looked at are pretty generic. Others, like this one (PDF), would require an extremely liberal view of the term "copy and paste."
How dare they copy/paste those blank lines!
I'm really sorry, but there was some code that was already written that was just too good to pass up for the project I was on:
#include
int main(int argc, char* argv[])
{
printf("Hello World!\n");
return 0;
}
Now that I'm using Java, it won't happen again.
Die, Monster, Die!
And here I always thought that libelf was the version of the libel() function that returned a nicely formatted incorrect defamatory statement.
Just don't forget to pay your SCO licensing fees you cock-smoking teabaggers!
Okay. Now I'm really confused. What does Sarah Palin have to do with SCO???
Wollt ihr den totalen Krieg?
I learned perl from someone who named all his variables with variations on "foo" and "bar". Back in those days, if I was writing something short and simple enough, it was hard for me to break the habit of naming things $foo, $bar, $boo, $far, $foofoo, etc. I'll bet a lot of our code looked like it was from the same person :)
The CB App. What's your 20?
Just don't forget to pay your SCO licensing fees you cock-smoking teabaggers!
Okay. Now I'm really confused. What does Sarah Palin have to do with SCO???
The approximate IQ of the management.
Looks like I typo'd = instead of ==, which I guess only proves that I review my joke code more thoroughly than SCO reviewed their actual code.
If this paragraph is indicative of your general level of knowledge about the history of Unix, you might want to look into ELF and how it got into Unix. I can tell you this however: it didn't came from Berkeley. The various BSD derivatives got it from SysV long after the fact.
Also you might want to spend about ten more seconds checking out the PDFs at the linked site, not just the one linked by the knucklehead kdawson. It's not simply header files. There is actual code. The similarities in code flow, layout, variable names, filenames, etc. are conclusive. The linux contributor didn't implement this code clean room-style based on the specification, plainly having used the Unix implementation as the source.
Dude, you ruined it. As written, you have a brilliant joke in C: the premise is bad (we're beating a dead horse), the plan is questionable (we're directly comparing a pointer and a string literal), and the execution is sloppy (thanks to the typo, we're testing the result of a non-zero assignment, so the horse is beat forever regardless of liveliness).
This is pretty much the story of SCO.
The PDFs are machine generated. I ran the same program using a copy of Moby Dick and the Microsoft EULA, it produced damning evidence that the programmers had copied them word for word into their source code.
No sig today...
That's the kind of analogy that Hitler would have made.
If you were blocking sigs, you wouldn't have to read this.
Do lambda functions not count as metaphors?
When our name is on the back of your car, we're behind you all the way!