Slashdot Mirror


Open Source Community Approaches SCO

An anonymous reader writes "eWeek has an article about the open source community approaching SCO. SCO now says there are over a million lines of offending code in Linux and they still won't show them to anybody."

10 of 521 comments (clear)

  1. Over 1,000 by Marx_Mrvelous · · Score: 5, Interesting

    Over 1 mil? Does anyone know how many lines of code there are in the linux kernel?

    --

    Moderation: Put your hand inside the puppet head!
  2. Heise News shows a code: by Anonymous Coward · · Score: 4, Interesting

    Heise News shows the code:
    http://www.heise.de/newsticker/data/jk-19.0 8.03-00 0/imh1.jpg

    The code seems to come from arch/ia64/sn/io/ate_utils.c, copyright by SGI:
    http://www.funet.fi/pub/Linux/PEOPLE/Linus/v 2.4/pa tch-html/patch-2.4.19/linux-2.4.19_arch_ia64_sn_io _ate_utils.c.html

    Does this code come from:
    http://minnie.tuhs.org/UnixTree/V5/usr/sys/ ken/mal loc.c.html
    http://minnie.tuhs.org/UnixTree/V7/usr /sys/sys/mal loc.c.html

    1. Re:Heise News shows a code: by hotair · · Score: 4, Interesting
      Am I missing something or are there syntax errors in the code in the jpeg image pointed to by the parent?
      if (size==0)
      return) ((ulong_t NULL);
      ...

      In which language does this compile?

  3. Heise News shows code by Anonymous Coward · · Score: 5, Interesting

    Heise News shows code:
    http://www.heise.de/newsticker/data/jk-19.0 8.03-00 0/imh1.jpg

    The code seems to come from arch/ia64/sn/io/ate_utils.c, copyright by SGI:
    http://www.funet.fi/pub/Linux/PEOPLE/Linus/v 2.4/pa tch-html/patch-2.4.19/linux-2.4.19_arch_ia64_sn_io _ate_utils.c.html

    Does this code come from:
    http://minnie.tuhs.org/UnixTree/V5/usr/sys/ ken/mal loc.c.html
    http://minnie.tuhs.org/UnixTree/V7/usr /sys/sys/mal loc.c.html

    1. Re:Heise News shows code by mocm · · Score: 4, Interesting

      And did you read the "encrypted" text below the commentary (greek letters) on the Unix side:
      As part of the kernel evolution towards modular naming, the functions malloc and mfree are being renamed to rmalloc and rmfree. Compatibility will be maintained by the following asembler code: (also see mfree/rmfree below)

      There is not even C code following. So SCO copied the commentary and than put something else in the file.

      --
      ***Quis custodiet ipsos custodes***
  4. Isn't samba GPL by nuggz · · Score: 4, Interesting

    How can they distribute samba?
    It is GPL, and they are arguing it is an invalid license.

    Unless the agree to the GPL, they can't distribute samba. Isn't this a stupid strategy?

    Here is the linke to the story, look at the bottom of it.
    http://news.com.com/2100-1016_3-5065286.html? tag=f d_lede1_hed

  5. C'mon, SCO, Show SOME lines by Esion+Modnar · · Score: 4, Interesting
    I mean if you have a million lines of your code in there, what's a mere hundred lines? Or ten?

    That way, even if everybody ran off and fixed those lines, you still have well over 900,000 lines of evidence (according to you) in your back pocket.

    And you would gain (maybe) some credibility. Not to mention what it'd do to your stock price.

    --

    They say the first thing to go is your penis. Well, it's either that or your brain. I forget which...
  6. Contract issue lines , not copyright lines by LightSail · · Score: 5, Interesting

    Darl is using a smoke screen: the million lines are not SCOX copyrighted, They were Sequent and IBM copyright. SCOX has a small chance of proving contract violation, but cannot prove copyright claim to Sequent/IBM code. Even winning the lawsuit does not give SCOX the copyright status to the donated code. The SCOX copyrighted code that may be in the Linux kernel is most likely either BSD, previously published algorisms, an open standard or hardware vendor release. These are not exclusive to SCOX. If SCOX had actual hard evidence, they would be using it to prove the point with a small public display. Any public display of code would easily be connected to the actual source outside of SCOX, so no show without nda. My feeling is that none of Linux is an actual copyright violation of SCOX copyright. This entire situation is a Hail Mary to increase market cap of SCOX, then use that value to buy profitable companies. Once SCOX has converted the inflated stock into additional sources of income, they will settle and rename the company to reflect its new identity. They may even end up by donating UNIX to open source to make amends, once they have milked the lawsuit and publicity for every dollar possible.

  7. License change by coyote-san · · Score: 5, Interesting

    I'm not sure how many contributers there are to the Samba project, but it's almost certainly far fewer than to the Linux kernel, GNU tool chain, etc.

    The bottom line is that they may be able to take direct action: change the license to "GPL-SCO." That's a stock GPL license with an extra clause superceding all others and explicitly prohibiting the use of the software on SCO systems, on any system owned by SCO regardless of the OS used, or distribution in any form by SCO or its successors. Finally, since SCO is claiming that none of these licenses are valid anyway there would be a final clause inserted by the lawyers that basically say that if the rest of the license is invalidated then SCO owes a licensing fee of US$1,000,000,000 per CPU, payable immediately. A billion dollars/CPU to the people who actually wrote the code is no less unreasonable than SCO trying to collect a kilobuck/CPU from Linux users who never invited SCO to the table.

    In short, if they want to support MS products but refuse to accept the standard license, they can damn well write the code themselves. The same applies to any other application they use.

    This is a bit more direct that what the GCC group is supposedly considering - dropping SCO hardware from the list of supported hardware - but it's clear that SCO isn't going to stop until the feds get off their ass and start prosecuting these clowns.

    --
    For every complex problem there is an answer that is clear, simple, and wrong. -- H L Mencken
  8. SCO reminds me of Senator Joe McCarthy: by Futurepower(R) · · Score: 4, Interesting


    From the Slashdot story: "SCO now says there are over a million lines of offending code in Linux and they still won't show them to anybody."

    This reminds me of Senator Joseph McCarthy's 1950 Communists in the State Department speech. See the end of the article for a quote from Senator McCarthy:

    "I have in my hand fifty-seven cases of individuals who would appear to be either card-carrying members or certainly loyal to the Communist Party, but who nevertheless are still helping to shape our foreign policy."

    Senator Joseph McCarthy said he would show Dean Acheson, then U.S. Secretary of State, the list, but only under special conditions that often changed. McCarthy said: "It would be a waste of effort to give Acheson the names, then have him deny they are Communists and we can not get the records."

    The number of Communists McCarthy said were in the U.S. State Department also often changed, too. Soon it was "81 subversives":

    The article cited above says, "Senator Lucas of Illinois, Democratic leader, repeatedly tangled with McCarthy, who also said he has case histories of 81 subversives--including what he called a 'big three'--who are working in and with the State Department. Lucas challenged McCarthy to name names. McCarthy refused, saying Lucas or any other interested authorities could get the names at McCarthy's office."

    "The Senate voted 67 to 22 to censure McCarthy" (See the end of the article.) "Senator Joseph Raymond McCarthy died soon after the censure, at the age of 48, of hepatitis and liver disease related to alcoholism."

    Senator McCarthy gave many people a big Red scare. However, in the end, everyone realized that he was a liar.