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."

25 of 578 comments (clear)

  1. Shocking by Kenoli · · Score: 4, Funny

    How dare they copy/paste those blank lines!

    1. Re:Shocking by bsDaemon · · Score: 2, Funny

      between that and pre-processor #include directives from the standard C library and POSIX stuff, well... damn. How could any judge have failed to see this!? /sarcasm

  2. Even if the Linux folks didn't, I did by wandazulu · · Score: 5, Funny

    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.

    1. Re:Even if the Linux folks didn't, I did by mysidia · · Score: 3, Funny

      Are you sure it hasn't already happened again?

      // hello.java
      /** This application greets the world.
        *
        * @Deprecated Earth has been destroyed by global warming, this is superceded by the goodbye  class
        */
      @Deprecated public class hello
      {
              public static void main(String args[])
              {
                 System.out.println("Hello World!");
              }
      }

    2. Re:Even if the Linux folks didn't, I did by Anonymous Coward · · Score: 1, Funny

      That won't compile. Include what?

  3. SCO! by Anonymous Coward · · Score: 3, Funny

    Die, Monster, Die!

    1. Re:SCO! by Anonymous Coward · · Score: 1, Funny

      How do you kill that which is already dead?

      Kill the parent process.

      Let's all hope SCO's parent process isn't init...

    2. Re:SCO! by Mathinker · · Score: 1, Funny

      That which is not dead may eternal lie
      And in strange eons even death may die

      Burma Shave!

    3. Re:SCO! by deniable · · Score: 2, Funny

      Parrot's not dead, it's still in beta.

  4. Re:libelf!?! by olsmeister · · Score: 5, Funny

    And here I always thought that libelf was the version of the libel() function that returned a nicely formatted incorrect defamatory statement.

  5. Re:What's so liberal about it? by Anonymous Coward · · Score: 1, Funny

    Slightly rearranged? That much rearrangement (plus adding comments and making sure it all still worked properly) would have taken more effort than just writing the damn thing from scratch!

  6. Re:First post by SpongeBob+Hitler · · Score: 2, Funny

    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?
  7. Re:What's so liberal about it? by Anonymous Coward · · Score: 1, Funny

    I'm sure there's a ton of other UNIXes out there that have the same line of code.

    And they all infringe our copyrights!

    - SCO

  8. Re:More details and downloadable archive by bennomatic · · Score: 5, Funny

    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?
  9. Re:More details and downloadable archive by Anonymous Coward · · Score: 1, Funny

    i can put it on look.at.datfukkendog.com

  10. Re:First post by JavaBear · · Score: 5, Funny

    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.

  11. Re:It's only a header file by Anonymous Coward · · Score: 1, Funny

    I've heard that in the lawyer business, page numbers are copyrighted.

  12. Re:Found this in SCO's code... by Legion303 · · Score: 3, Funny

    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.

  13. Re:First post by Score+Whore · · Score: 3, Funny

    Going further on a limb I'm also guessing this is why they would never release any of the alleged violations. In days a website similar to groklaw would be up in for everyone to review, identify and mark the source of the "violation." ie, this is a struct for the elf library specification or this is a header of a BSD library. (Remember that BSD ancestry is likely still there in large chunks)

    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.

  14. In Other News... by pandrijeczko · · Score: 1, Funny

    ...Chuck McBride, a Texas beef farmer and brother to the SCO CEO, has made claims that Linux is responsible for the still-births of two of his calves this year...

    --
    Gentoo Linux - another day, another USE flag.
  15. Re:Found this in SCO's code... by Wuhao · · Score: 3, Funny

    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.

  16. Re:What's so liberal about it? by Anonymous Coward · · Score: 1, Funny

    ... a hole in the wall as a way of getting in and out of a room.

    ... or a lady.

  17. Re:First post by Joce640k · · Score: 3, Funny

    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...
  18. Re:More details and downloadable archive by Rogerborg · · Score: 5, Funny

    Trying to imply that this is some nonsense that should be dismissed just because you like Linux is like playing down and ridiculing the evidence of the murder of Hans Reiser's wife because you like ReiserFS. It's even sillier in some ways because Linux isn't at stake in the case like ReiserFS was. (An extreme analogy I know, but valid).

    That's the kind of analogy that Hitler would have made.

    --
    If you were blocking sigs, you wouldn't have to read this.
  19. Re:More details and downloadable archive by camperdave · · Score: 3, Funny

    Do lambda functions not count as metaphors?

    --
    When our name is on the back of your car, we're behind you all the way!