Slashdot Mirror


Not Quite Dead: SCO Linux Suit Against IBM Stirs In Utah

An anonymous reader points to a story in the Salt Lake Tribune which says that The nearly defunct Utah company SCO Group Inc. and IBM filed a joint report to the U.S. District Court in Salt Lake City saying that legal issues remain in the case, which was initiated in 2003 with SCO claiming damages of $5 billion against the technology giant, based in Armonk, N.Y. That likely means that U.S. District Judge David Nuffer, who now presides over the dispute, will start moving the lawsuit — largely dormant for about four years while a related suit against Novell Inc. was adjudicated — ahead. What kind of issues? In addition to its claims of IBM misappropriation of code, SCO alleges that IBM executives and lawyers directed the company's Linux programmers to destroy source code on their computers after SCO made its allegations. The company's other remaining claims are that IBM's actions amounted to unfair competition and interference with its contracts and business relations with other companies. IBM has remaining claims against SCO that allege the Utah company violated contracts, copied and distributed IBM code that had been placed in Linux and that SCO created a campaign of "fear, uncertainty and doubt" about IBM's products and services because of the dispute over Unix code.

8 of 170 comments (clear)

  1. Oh, for Pete's sake. Not again! by some+old+guy · · Score: 3, Interesting

    Seriously, is there no limit to this barratry-fest? Surely the judge must tire of it eventually.

    --
    Scruting the inscrutable for over 50 years.
    1. Re:Oh, for Pete's sake. Not again! by a_n_d_e_r_s · · Score: 4, Interesting

      They have had like 4-5 judges in this case already.

      The judges has done alot to try and get away from this case.

      --
      Just saying it like it are.
  2. IBM should put SCO out of misery by sxpert · · Score: 4, Interesting

    Can't IBM just buy whatever remains of SCO for scrap and shoot it down for good ?

    1. Re:IBM should put SCO out of misery by drinkypoo · · Score: 4, Interesting

      Take it over by force, find evidence that it was a sock puppet, sue the lawyers

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:IBM should put SCO out of misery by Langalf · · Score: 3, Interesting

      Seriously, the SCO we know and hate was NEVER a good company. Santa Cruz Operations was an OK provider of Unix, but SCO Group was little more than a poor caretaker of the legacy.

  3. Destruction of documents by bernywork · · Score: 3, Interesting

    I hope they kept everything, SCO was going to start destroying stuff in 2013.

    http://www.groklaw.net/article...

    --
    Curiosity was framed; ignorance killed the cat. -- Author unknown
  4. What will it take to kill SCO permanently? by TomTraynor · · Score: 3, Interesting

    Maybe a laminated stake through the hear (wood & silver soaked in garlic and holy water). Then stuffed in a coffin placed in a double hulled container, the container gap is filled with holy water and garlic juice. Put into a rocket and launched into an orbit near the sun. Even then I would be willing to bet it would get out and return.

    --
    Panic now, beat the rush!
  5. Re:Was SCO really that bad? by walterbyrd · · Score: 1, Interesting

    I agree: systemd has damaged Linux far worse than scox.

    IMO: both systemd, and scox, stem from the same idea: companies like Linux being free, but dislike not being able to own Linux.

    IMO: Red Hat, the company behind systemd, is much smarter, and is much more likely to successfully steal Linux.