Slashdot Mirror


13-Year-Old Linux Dispute Returns As SCO Files New Appeal (theinquirer.net)

An anonymous reader quotes a report from THE INQUIRER: Now-defunct Unix vendor, which claimed that Linux infringed its intellectual property and sought as much as $5 billion in compensation from IBM, has filed notice of yet another appeal in the 13-year-old dispute. The appeal comes after a ruling at the end of February when SCO's arguments claiming intellectual property ownership over parts of Unix were rejected by a U.S. district court. That judgment noted that SCO had minimal resources to defend counter-claims filed by IBM due to SCO's bankruptcy. "It is ordered and adjudged that pursuant to the orders of the court entered on July 10, 2013, February 5, 2016, and February 8, 2016, judgement is entered in favor of the defendant and plaintiff's causes of action are dismissed with prejudice," stated the document. Now, though, SCO has filed yet again to appeal that judgement, although the precise grounds it is claiming haven't yet been disclosed.

13 of 233 comments (clear)

  1. Zombie by DarkOx · · Score: 5, Insightful

    Can't someone kill this zombie process

    --
    Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    1. Re:Zombie by MrKaos · · Score: 5, Funny

      Can't someone kill this zombie process

      No, it's maintained by systemd now.

      --
      My ism, it's full of beliefs.
    2. Re:Zombie by mikael · · Score: 5, Insightful

      I've seen it happen a lot on servers. It usually happens because the process is already suspended while waiting for a resource to be freed. Like trying to get an exclusive lock on a network shared file after the connection is lost. As it is waiting for a response from the network, it's put in a suspended state. But since there is no connection, there's never going to be a reply. So it just waits and waits.

      Sending a kill signal might nudge it closer to the afterlife and get local resource freed, but when remote resources on network servers are tried to be released, it locks up.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    3. Re:Zombie by Ixokai · · Score: 4, Interesting

      It hasn't really been about "them" getting anything for awhile now, is my perspective. There's a certain pile of cash and the lawyers want it and they'll get it (ahead of other creditors) by actively perusing lawsuit.

      I just thought the pile ran out, but if that lawfirm filed again, clearly there's money somewhere they can grab.

      This stopped being about anything but billable hours... years ago.

    4. Re:Zombie by Dutch+Gun · · Score: 4, Insightful

      I'll give SCO $500 just to go away.

      Well, it's a good thing it's not up to you then. That's precisely what IBM is refusing to do, because that gives these slimes a precedent and an opportunity to go after potentially softer targets. Good on IBM for not taking the easy way out.

      You're over-thinking this. This is absolutely still about money. It's just lawyers on contingent (meaning no one is paying them) just putting in a minimal amount of effort and expenses to file a few more court documents, hoping for a big miracle payday. Sure, the odds are low, but when the potential payout is massive, why not?

      --
      Irony: Agile development has too much intertia to be abandoned now.
    5. Re:Zombie by DarkOx · · Score: 4, Informative

      basically no process can die on its own.
      once exit() is called its the job of parent to read the exist status. If the parent process does not do it then the process remains a zombie.

      Usually the fix for the leak is to kill the parent. Doing so allows init to read the parents exit status, and the now orphaned children are then adopted by init which will read their status and clean them up.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
  2. Re:SCO actually got a bad deal here by Zontar+The+Mindless · · Score: 5, Funny

    Nice to know that Darl still reads Slashdot.

    --
    Il n'y a pas de Planet B.
  3. March 31 by ChunderDownunder · · Score: 4, Funny

    A bit early to be publishing these April 1 Zombie Apocalypse stories, no?

  4. Follow the money by Anonymous Coward · · Score: 5, Insightful

    Who is funding the appeals at this point?

  5. Re:SCO actually got a bad deal here by Anonymous Coward · · Score: 5, Informative

    Interesting take on reality.

    This might give you some pointers on what they did show, why they didn't own it, and why trying to claim copyright on POSIX APIs is a daft thing to do.

    https://en.wikipedia.org/wiki/SCO/Linux_controversies#SVRx_code_allegedly_in_Linux

    However code was (allegedly) found that had been illegally copied into SCO's Unix products from Linux as part of it's Linux Kernel Personality feature.

  6. Re:SCO actually got a bad deal here by nikkipolya · · Score: 5, Informative

    If I remember correctly, you are talking absolute non-sense Mr. Daryl McBride.

    The few infringing lines of code that they claimed and showed were actually UNIX header files and some API's. Novell clarified that UNIX header files and API's are in the public domain having been transferred to UNIX Sys Labs. SCO showed code from 'Berkeley Packet Filter' which then was shown to be under the BSD license. Then they went to show some macro definitions for silly things like MAX, MIN. When it got clarified by Torvalds that there were very very few ways to implement those silly macros in the *right* way, SCO just went mum. SCO refused to show anymore infringing source code and went about selling legal protection from "we want tell you" product. Intel, IBM and a few other companies pooled some money and told small and medium companies that the pooled money would help them defend against the stupid cases SCO was threatening to file against them if they did not pay their legal protection fees. Miscrosoft on the contrary went ahead and purchased legal protection from SCO for their UNIX tool-kit for windows, in order to help fund SCO in their legal litigation and there by undermine Linux.

    Basically SCO lacked the ability to innovate and tried to become a troll.

  7. Re:SCO actually got a bad deal here by Anonymous Coward · · Score: 4, Interesting

    Hmmm, actually not a true statement. I work for the US Courts and a surprising many of them are at least technically literate; of course there are some that are complete Luddites and have no business being on the bench in this day and age. Then there are some (thinking 2nd Circuit) who know a surprising amount about the technology and how to employ it in the courts. We have judges using the iPad to review filings, their dockets, orders, and pleadings while commuting to work. When you have life tenure on the bench sometime the only way to get them off the bench is on a stretcher or in a body bag. Posting anonymously because I work for the US Courts in the technology division; I have a 5 digit /. id but I want to keep my job.

  8. Re:SCO actually got a bad deal here by DickBreath · · Score: 4, Informative

    SCO was ordered by the court THREE TIMES to show their source code to the court. That is a different thing than a PR dog and pony show. SCO whined. Stalled. The court had to order them three times.

    Eventually the court give SCO a third and final deadline. Dec 22, 2005. Disclose ALL allegedly misused materials in Linux by then.

    What did we get? A lot of hand waving and nonsense. Nothing substantial.

    After months more arguing, the court tossed out 2/3 of that. Of the remaining 1/3, the magistrate judge (Wells) was quite skeptical. But technically it wasn't crazy enough to throw out with the other 2/3, so SCO could keep it, although they probably wouldn't get anything out of it.

    A side show in this matter was that SCO did not own any copyright in Unix in the first place. Years later, by 2007, the court finally concluded that SCO didn't even own any copyright in Unix. So they have no standing to sue in the first place. (eg, I can't sue you for stealing Jane's tires. Only Jane has standing to sue you for that.)

    There are many more facets to this entire fiaSCO. And none of them are good for the SCOundrels.

    On the Friday before SCO's scheduled trial to start on Monday in Sept 2007, where after years of saying they wanted to get their day in court, SCO declared bankruptcy. On the eve of the trial that would give them their supposed victory. And SCO was still financially solvent.

    Everything about this entire farce stinks to high heaven.

    --

    I'll see your senator, and I'll raise you two judges.