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.

233 comments

  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 Anonymous Coward · · Score: 0

      Just to be sure...

      for KILLPID in `ps ax | grep 'sco' | awk ' { print $1;}'`; do
          kill -9 $KILLPID;
      done

    3. Re:Zombie by Anonymous Coward · · Score: 0

      5 billions / 13 years of whining is a nice assload of money.

    4. Re:Zombie by Anonymous Coward · · Score: 2, Funny

      They tried and that's why SCO filed the appeal, apparently they own the rights to 'kill', 'killall' and derivatives.

    5. Re:Zombie by Anonymous Coward · · Score: 0

      killall -o 13y sco

      should still work fine even with systemd.

    6. Re:Zombie by korgitser · · Score: 1

      Sometimes a process gets so zombied it actually cannot die anymore. Do not remember the details, but happened to me once. Only a reboot will fix these.

      --
      FCKGW 09F9 42
    7. Re: Zombie by Anonymous Coward · · Score: 0

      fuser -km /

    8. 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
    9. Re:Zombie by Lisias · · Score: 1

      kill -1 1

      --
      Lisias@Earth.SolarSystem.OrionArm.MilkyWay.Local.Virgo.Universe.org
    10. Re:Zombie by Phreakiture · · Score: 2

      while ps -ef | grep sco | grep -v grep
      do
      pkill -9 sco
      done

      --
      www.wavefront-av.com
    11. Re:Zombie by Anonymous Coward · · Score: 0

      You have been assimilated. Resistance is futile.

    12. Re:Zombie by houghi · · Score: 1

      We could, but we would need to reboot the copyright and trademark process.

      --
      Don't fight for your country, if your country does not fight for you.
    13. Re:Zombie by silentcoder · · Score: 1

      I've never seen that on Linux. In fact I've hardly ever seen it on a modern Unix. The one where I saw it a *lot* was HPUX. A zombie process on at least some HPUX versions was basically unkillable, it just flat-out ignored a -9.

      --
      Unicode killed the ASCII-art *
    14. Re:Zombie by KGIII · · Score: 2

      Some of the people here, some of the ones I communicate with off-list, have had in my home, and have visited in my travels - some of them, have children that are younger than these shenanigans from SCO.

      At this point, I'll give SCO $500 just to go away. I don't want them getting any money but I'll give it to them if they promise to go away and never return. The suit certainly is no longer about being backed by Microsoft in order to discredit Linux or open source. That horse has already left the barn and Microsoft is doing "okay" at getting used to it. It can't be about money, they can't possibly think they're going to come out ahead after all of this.

      So, what the hell is the point? I really can't think of a good reason for them to be even bothering with this - or any other suit. I can't think of anything to be gained from it - it's not like they're going to win this or any other suit they try to throw at anyone. Someone, somewhere, is urging them to continue. Why? I believe they were still facing a suit from one of the other players - just so it buries them deep enough that they should be dead.

      Actually, shouldn't they be dead in the water already? Who is paying for the lawyers? I guess we'll have to wait for that to come out, just like we'll have to wait for the papers to come out that explain their next argument. Someone, somewhere, must think there's a chance of succeeding and is willing to foot the bill, at least for this? Maybe? Who? Why?

      Since day one it has looked, at least to a layman, like it was not going to go anywhere. I still haven't been billed my $699 for my copy of Linux. In fact, at last count, I was streaming more than 140 different versions (some are older versions - older LTS and things like that). Boy am I gonna owe 'em a hefty sum of money when they win! *snickers*

      --
      "So long and thanks for all the fish."
    15. Re:Zombie by KGIII · · Score: 1

      It's not 1995 any more. You can just load it up in HTOP and use a mouse!

      --
      "So long and thanks for all the fish."
    16. 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.

    17. Re:Zombie by whoever57 · · Score: 1
      while ps -ef | grep [s]co

      FTFY

      --
      The real "Libtards" are the Libertarians!
    18. Re:Zombie by RabidReindeer · · Score: 1

      You have been assimilated. Resistance is futile.

      Actually, a good idea. Can't some judge just rule that they don't have enough to pay the legal expenses and order the company forfeited to IBM lock, stock, and barrel?

      IBM can start by firing the SCO people and handing them lead parachutes instead of the usual golden ones. Along with termination terms that forbid ever getting involved with any Unix-like product ever again.

      Then it can grind up the rest of the company into a fine power and distribute it over Chernobyl.

      And just for good measure, destroy all records that SCO ever had back to the Beginning of Time.

      Heck, ravening corporate behemoths need to be good for something, anyway.

    19. Re:Zombie by phrostie · · Score: 1

      or we could wait till after Aprilfools day and see if it's real.

      it's that time of year.
      believe nothing.

    20. Re:Zombie by Anonymous Coward · · Score: 0

      oh man, a 3 digit uid! ebay me some!

    21. Re: Zombie by Anonymous Coward · · Score: 0

      Though I've actually come to like systemd better can I just say: Ha!

    22. Re:Zombie by Jason+Levine · · Score: 1

      Some of the people here, some of the ones I communicate with off-list, have had in my home, and have visited in my travels - some of them, have children that are younger than these shenanigans from SCO.

      My oldest son was born in the same year that the SCO-IBM lawsuit began - albeit five months later. He's having his Bar Mitzvah later this year. My youngest son is turning 9 in a couple of months and was born in the thick of the SCO-IBM/SCO-Novell /SCO-Everyone muck.

      --
      My sci-fi novel, Ghost Thief, is now available from Amazon.com.
    23. Re:Zombie by Z00L00K · · Score: 1

      Looks like a shotgun wedding.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    24. Re:Zombie by tinkerghost · · Score: 1

      Actually, the lawyers don't want to do anything. They signed a contract to get paid up front through the end of the case. They have been working on their own dime for years now. What I want to know is who in the bankruptcy court authorized them to spend money to file the paperwork?

    25. Re:Zombie by mlts · · Score: 1

      I saw it on early versions of Solaris 2, back in the mid to late 1990s, where there would be a ton of zombie processes, they would laugh at a -9, and the only way to deal with them was a reboot, and even then, there almost certainly would be a NFS hang, preventing the machine from completely shutting down, so most likely a reset would be needed (which meant a force fsck of all drives because back then, journaling filesystems were not common.)

      It makes me glad that operating systems eventually almost have solved this. Software RAID is doable in multiple ways (btrfs, LVM2, md-raid, ZFS), filesystems have rollback functionality to keep consistant, HDDs have moved to SSDs which have a different set of problems, etc.

      I might encounter a zombie process here and there, but the only time it gets noticable is with a drive that is on the edge of disgorging its contents into oblivion, or network/storage fabric issues.

    26. 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.
    27. 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
    28. Re:Zombie by bev_tech_rob · · Score: 1

      Can't someone kill this zombie process

      I wonder if wooden stakes and holy water would work?

      --
      You're messin' with my Zen Thing, man.....
    29. Re:Zombie by bev_tech_rob · · Score: 1

      Better yet, give them blindfolds and cigarettes and tell them to line up over by that big brick wall...

      --
      You're messin' with my Zen Thing, man.....
    30. Re:Zombie by PPH · · Score: 1

      So use the systemd halt service.

      --
      Have gnu, will travel.
    31. Re:Zombie by JustBoo · · Score: 1

      They tried and that's why SCO filed the appeal, apparently they own the rights to 'kill', 'killall' and derivatives.

      I think Shakespeare said it best: "The first thing we do, let's killall the lawyers."

      I suspect by now, with all the parasitic legal fees, SCO is now mostly owned by blood-sucking 'lowya's.' Where is Van Helsing when we really need him.

    32. Re:Zombie by gstoddart · · Score: 1

      So, what the hell is the point? I really can't think of a good reason for them to be even bothering with this

      It really is simple:

      Greedy douchebags convinced they own something and seeking to capitalize on it.

      Actually, shouldn't they be dead in the water already? Who is paying for the lawyers?

      My guess, somewhere along the line the "property" SCO claims got transferred to some consortium of lawyers (wikipedia tells me the latest name is "TSG Operations, Inc.") and other bottom feeding assholes convinced they're going to eventually hit paydirt.

      Someone has assigned a monetary value to that, and until all possible venues are finally killed off (and I have no idea what that entails), whatever deluded crooks claim to own it will keep coming. Someone is convinced they're sitting on a gold mine, and if they can establish the right precedent can go on a binge of shaking down the world.

      Essentially the Ponzi scheme has new owners.

      --
      Lost at C:>. Found at C.
    33. Re:Zombie by MrKaos · · Score: 1

      And just for good measure, destroy all records that SCO ever had back to the Beginning of Time.

      We should probably find everyone who has ever been involved, move them to another planet, erase their timeline, remove every atoms interaction with the universe then nuke them from orbit, just to be sure.

      --
      My ism, it's full of beliefs.
    34. Re:Zombie by Anonymous Coward · · Score: 0

      I don't watch that zombie show, but it seems like this would be a good plot item.
      A zombie, that no matter what you do, just keeps coming, forever.
      "Oh, no! It's a Darl!"

    35. Re:Zombie by Anonymous Coward · · Score: 1

      April 1 in Japan?

      Probably not.

      But it's almost time. In a few hours, Slashdot goes on vacation. The have a robot post jokes composed of random strings for 24 hours. Users are expected to go to science daily or the onion during this outage. (users are expected to return the next day, please).

    36. Re:Zombie by Bob+the+Super+Hamste · · Score: 1

      I would add in silver bullets probably need to be uses too.

      --
      Time to offend someone
    37. Re:Zombie by fahrbot-bot · · Score: 1

      Can't someone kill this zombie process

      Not for a while, SCO just got signed as a character on The Walking Dead.

      --
      It must have been something you assimilated. . . .
    38. Re:Zombie by Anonymous Coward · · Score: 0

      I vote for an extension of the psmisc (http://psmisc.sourceforge.net/) package.
      # killall --sco

    39. Re:Zombie by JustAnotherOldGuy · · Score: 1

      while ps -ef | grep darlmcbride | grep -v grep
      do
      pkill -9 darlmcbride
      done

      --
      Just cruising through this digital world at 33 1/3 rpm...
    40. Re:Zombie by Immerman · · Score: 1

      Let's leave Chernobyl out of it - I'm pretty sure SCO evolved from some sort of parasitic pond scum, so grinding it up is unlikely to kill it, and I'd hate to see what it mutates into with all that radiation at its disposal.

      --
      --- Most topics have many sides worth arguing, allow me to take one opposite you.
    41. Re:Zombie by Immerman · · Score: 1

      Well that's convenient - our legal system could really use a reboot anyway, maybe it will even remain a justice system for a while.

      --
      --- Most topics have many sides worth arguing, allow me to take one opposite you.
    42. Re:Zombie by Anonymous Coward · · Score: 0

      You can't kill zombie processes because they're already dead. The system is keeping the dead process around so that their parent can read their status, which essentially makes them a bug/resource leak of the process that created them.


      #include <stdio.h>
      #include <stdlib.h>
      #include <string.h>
      #include <unistd.h>
      #include <sys/wait.h>

      int main() {
          pid_t child = fork();
          int status;

          if(child < 0) {
              perror("fork");
              return EXIT_FAILURE;
          }

          if(child == 0) {
              printf("I'm the child. I'm going to die and become a zombie.\n");
              return EXIT_SUCCESS;
          }

          printf("I'm the parent. I'm going to neglect my child (pid=%d) for a minute.\n", (int)child);
          sleep(60);

          printf("I'm cleaning up my smelly zombie child now.\n");
          waitpid(child, &status, 0);

          if(WIFEXITED(status)) {
              printf("My child killed itself. The suicide note reads 'exit status = %d'\n", WEXITSTATUS(status));
          } else if(WIFSIGNALED(status)) {
              printf("My child was murdered by signal '%s'.\n", strsignal(WTERMSIG(status)));
          } else {
              printf("My child died under mysterious circumstances.\n");
          }

          printf("I'm a terrible parent. Give me a minute.\n");
          sleep(60);

          return EXIT_SUCCESS;
      }

    43. Re:Zombie by Anonymous Coward · · Score: 0

      for KILLPID in `ps ax | grep 'sco' | awk ' { print $1;}'`; do
              kill -9mm $KILLPID;
      done

      FTFY

    44. Re:Zombie by Hognoxious · · Score: 2

      At this point, I'll give SCO $500 just to go away.

      That's $199 short.
          Signed,
          Darl.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    45. Re:Zombie by sjames · · Score: 1

      I'm wondering why not just revoke their charter at this point. They're out of cash, and long ago got rid of anyone needed to do any sort of economically productive work. There is zero chance the company will ever return to any economic activity that is even vaguely in the public interest.

      At BEST, this is about a lawyer wanting to bill against a small pile of cash that should have been handed over to creditors by now anyway.

    46. Re:Zombie by sjames · · Score: 1

      If a 3rd party gives them $500 to just go away, it sets no precedent of any kind.

    47. Re:Zombie by jfbilodeau · · Score: 1

      Zombies are created when a process terminates but it's parent does not call wait() on it.

      Killing the negligent parent kills the zombie.

      --
      Goodbye Slashdot. You've changed.
    48. Re:Zombie by Anonymous Coward · · Score: 0

      This should never happen. It's a bug in the Kernel. The kernel manages the file handles / sockets / RAM and all other resources that it grants to processes, this is how it reclaims memory even thought some programs, esp. those using X11, never free some data structures. If the process is ending, there's no need to call free() a shit load of times beforehand because the OS knows what pages it granted to the process and will reclaim that memory.

      There should be no "deadlock" possible because the kernel can free any resource it wants. Indeed, Linux does just this. I've had to use a different kernel on embedded platforms because on Linux malloc() never fails. If malloc() runs out of RAM and swap space, then Linux just starts killing processes. You WILL get your RAM from malloc() even if it kills the entire system. I consider this a bug, but it works as intended according to kernel devs... If malloc() failed I might display a (preallocated) prompt to the user stating we've run out of memory, or perhaps free some resources and try again.

      Linux really is shit, it's the best free shit we have, but it's still shit.

    49. Re:Zombie by Stinky+Cheese+Man · · Score: 1

      Pro tip:

      Instead of: ps -ef | grep darlmcbride | grep -v grep

      Do this: ps -ef | grep [d]arlmcbride

    50. Re:Zombie by Dutch+Gun · · Score: 2

      Since we're apparently being pedantic here, they're not going to go away for $500 either.

      The point I'm making is that it's not a good idea to settle, because that just encourages more of the same behavior.

      --
      Irony: Agile development has too much intertia to be abandoned now.
    51. Re: Zombie by Anonymous Coward · · Score: 0

      you shoul read up on memory overcommit and how to turn it off. Also on process resource limits.

    52. Re:Zombie by Anonymous Coward · · Score: 0

      The original SCO wasn't a bad company...

      It just got infected... and is now a zombie.

    53. Re:Zombie by Anonymous Coward · · Score: 0

      It hangs... and doesn't really die.

      Just flails in the wind trying to find a foothold... :)

    54. Re: Zombie by TimMD909 · · Score: 1

      Cigarettes are unhealthy. Let them vape.

    55. Re:Zombie by Anonymous Coward · · Score: 1

      A zombie process ("Z" state) is already dead. It no longer holds any resources but remains in the process table until either its parent retrieves its exit status with wait() (or waitpid() or similar) or the parent no longer exists.

      You're probably thinking of processes in uninterruptable sleep ("D" state). These are waiting on a blocking system call which cannot be interrupted.

      The single most common cause of the "D" state is network file systems (NFS or SMBFS/CIFS). Operations on files (as opposed to pipes, sockets, ttys, etc) are typically uninterruptable because they aren't supposed to be able to block indefinitely, so there should be no reason to interrupt them.

      Fundamentally, the problem stems from trying to pretend that a remote system or a user-space process is actually a local hardware device with a bounded response time.

      This is part of the reason why many Unix admins will tell you that "NFS" stands for "Not a File System" (although its non-conformance goes far deeper than just having failure modes which file systems aren't supposed to have).

    56. Re:Zombie by Immerman · · Score: 1

      Agreed. The original SCO has essentially nothing to do with the malignancy currently bearing the name. At worst they were the first victim, but I don't think there's anything of them left.

      --
      --- Most topics have many sides worth arguing, allow me to take one opposite you.
    57. Re:Zombie by armanox · · Score: 1

      Just be warned that strsignal() doesn't exist on most UNIX platforms - I went to run your code for the fun of it and got:

      ld32: ERROR 33 : Unresolved text symbol "strsignal" -- 1st referenced by zombie.o.

      Eliminating strsignal from that line and changing %s to %d makes it all better

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
    58. Re:Zombie by sjames · · Score: 1

      And I was pointing out that nobody was suggesting a settlement of any kind. KGIII was suggesting (mostly in jest) that HE PERSONALLY would give them $500 so they would go away and he wouldn't have to read about them any more.

      But no, they wouldn't take such an offer. You can't bribe a disease.

    59. Re:Zombie by macs4all · · Score: 2

      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.

      IMHO, there's a special place in Hell for Developers that write code that waits for a handshake, but then don't put some sort of a reasonable timeout in the code. Really, even if we're talking about waiting for something to respond through a Dialup connection, if that resource isn't available in a couple of hours, it probably is safe to assume it ain't comin' back.

      So, unless you're writing code to collect data from outer space, there's absolutely no reason to "wait forever" (and even then, "forever" is too frickin' long)...

    60. Re:Zombie by Dutch+Gun · · Score: 1

      Isn't paying someone to end legal proceedings pretty much the definition of a settlement?

      But no, they wouldn't take such an offer. You can't bribe a disease.

      Well, good to see we agree on this point.

      --
      Irony: Agile development has too much intertia to be abandoned now.
    61. Re:Zombie by sjames · · Score: 1

      Isn't paying someone to end legal proceedings pretty much the definition of a settlement?

      Only if the offer comes from a party to the suit. But in general, settlements don't set precedent.

    62. Re:Zombie by Anonymous Coward · · Score: 0

      There was the idea to give SCO a copy of the 'linux' source code ... in paper
      maybe we should revive that?
      I offer a pack of 500 pages and the printer (shipping too)
      Let's bury them with paper

    63. Re:Zombie by Zeroko · · Score: 1

      Others mentioned the D state (uninterruptible sleep), but it is also possible for a process in R state (running) to be unkillable if it gets stuck in certain system calls (that usually finish quickly but can exhibit pathological behavior), which seems a bit worse as it sits there hogging 100% of a CPU core rather than just a process ID & a bit of RAM.

    64. Re:Zombie by Dutch+Gun · · Score: 1

      Well, I'm sure you're probably correct from a legal standpoint, but I think my point of "bad idea to pay off these arseholes" still stands. Fair enough?

      --
      Irony: Agile development has too much intertia to be abandoned now.
    65. Re:Zombie by guruevi · · Score: 1

      SCO's only "asset" is this case. This is just a strategy for the officers/lawyers of the company to squeeze the last remaining money out of the accounts before it's forced to give the remains to IBM (quote: "given SCO’s bankruptcy and its explanation that it has de minimis financial resources beyond the value of the claims on which the Court has granted summary judgment for IBM")

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    66. Re:Zombie by Anonymous Coward · · Score: 0

      What about server whose job it is to sit and wait for clients to connect? Does that need a timeout?

    67. Re:Zombie by KGIII · · Score: 1

      Yeah, someone above mentions that a group (consortium) of lawyers own the "property" now. Man, I've seen some crappy distros out there. I'm not gonna pay $699 for Puppy or Damn Small either - I want a discount for those!

      I really would give 'em $500 to go away, by the way. If we all chip a little in and offer it to them to go lay down next to their dish (selling us their "property") then... No, they still won't take that. Oh well, they can get nothing instead.

      --
      "So long and thanks for all the fish."
    68. Re:Zombie by Anonymous Coward · · Score: 0

      You can't kill a zombie process, because it's already dead. A zombie process is just the process descriptor, which is left behind so that the parent process can reap the exit result. If you kill the parent process, the zombie processes are re-parented to init, which then should use wait() to dispose of them.

      The "waiting for resources" bit may block the parent process, and prevent it from wai()-ing itself.

    69. Re: Zombie by ihtoit · · Score: 1

      oh, they're arguing about the safety of that now as well... to the point where they've had to invent a silhouette in attempts to stop people vaping up in public open spaces.

      --
      Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
    70. Re:Zombie by ihtoit · · Score: 1

      Alternatively, you know, just fucking destroy the brain case.

      --
      Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
    71. Re: Zombie by Anonymous Coward · · Score: 0

      s/9mm/15kV/

    72. Re:Zombie by JImbob0i0 · · Score: 1

      You're using pkill but then grepping the result of ps for the state of the while loop?

      while pgrep sco &> /dev/null
      do
          pkill -9 sco
      done

      Of course that will only kill sco once as as soon as no sco is in the process table the while loop will exit ... given how sco behaves though perhaps we should do:

      while true
      do
          if pgrep sco &> /dev/null
          then
              pkill -9 sco
          fi
      sleep 1
      done

    73. Re:Zombie by JImbob0i0 · · Score: 1

      or just use pgrep ...

    74. Re:Zombie by macs4all · · Score: 2

      What about server whose job it is to sit and wait for clients to connect? Does that need a timeout?

      You don't read so well, do you?

      I specifically limited that hypothetical "special place in Hell" to those Devs. who were writing code that waited for a HANDSHAKE.

      If you don't know the difference between that scenario and "waiting for a login", (which, BTW, is NOT what a "Server" "sits and waits for"), then you obviously shouldn't be commenting on my Post in the first place.

    75. Re:Zombie by Stinky+Cheese+Man · · Score: 1

      Thanks for the tip. I didn't know about that.

    76. Re:Zombie by david_thornley · · Score: 1

      No, SCO doesn't own those rights. However, if someone attempts to use them against SCO, SCO will file a court case arguing that they do.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    77. Re:Zombie by david_thornley · · Score: 1

      I believe that dousing the computer with holy water is likely to stop all zombie processes.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  2. Its a blast from the past by MichaelSmith · · Score: 1

    I can't wait.

  3. Garlick and wooden stakes needed ... by Alain+Williams · · Score: 2

    to prevent this blood sucking vampire from rising again. Can we ship some to the IBM lawyers ?

    1. Re:Garlick and wooden stakes needed ... by packrat0x · · Score: 1

      The lawsuit was dismissed "with prejudice", and the lawyers still filed an appeal. Apparently the only thing these lawyers understand is physical violence. Wooden stakes might help.

      --
      227-3517
    2. Re:Garlick and wooden stakes needed ... by Anonymous Coward · · Score: 0

      They should also bring holy water, axes, torches and lots of fuel to burn them with, then salt the ashes, put them in a sealed container and shoot it into the sun. Pack the rocket with a nuke... just to be sure.

    3. Re:Garlick and wooden stakes needed ... by Z00L00K · · Score: 3, Interesting

      The first point here is to figure out the individuals behind this and who's sponsoring them. Then publish who they are and see if they still are interested in pursuing the matter.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    4. Re:Garlick and wooden stakes needed ... by Z00L00K · · Score: 1

      Maybe what's needed is an exorcist.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    5. Re:Garlick and wooden stakes needed ... by TWX · · Score: 2

      The lawsuit was dismissed "with prejudice", and the lawyers still filed an appeal. Apparently the only thing these lawyers understand is physical violence. Wooden stakes might help.

      I would be very much amused if they're held in-contempt and thrown in jail for a couple of months.

      You know, just long enough to have some moderate real-world consequences.

      --
      Do not look into laser with remaining eye.
    6. Re:Garlick and wooden stakes needed ... by Anonymous Coward · · Score: 0

      Hopefully somebody will be pain in the ass to them.

    7. Re:Garlick and wooden stakes needed ... by Gort65 · · Score: 1

      Maybe what's needed is an exorcist.

      More like an Exocet.

    8. Re:Garlick and wooden stakes needed ... by cyberchondriac · · Score: 1

      It's like a bad sequel. Who'd want to watch "Jaws 17" ? .. they just don't get the hint, it's game over.

      --

      Look back up at my post, now look back down, you're on the Internet. Now look back up. I'm a signature.
    9. Re:Garlick and wooden stakes needed ... by Just+Some+Guy · · Score: 1

      What makes you think IBM lawyers are able to touch garlic and wooden stakes?

      --
      Dewey, what part of this looks like authorities should be involved?
    10. Re:Garlick and wooden stakes needed ... by Mike+Van+Pelt · · Score: 1

      Or a judge willing to say "What part of 'With Prejudice' is unclear to you? You did pass the bar, didn't you? Did you? Contempt of court, 90 days in jail, $100,000 fine. And I *will* repeat as necessary."

    11. Re:Garlick and wooden stakes needed ... by Areyoukiddingme · · Score: 1

      What makes you think IBM lawyers are able to touch garlic and wooden stakes?

      The Nazgul are allowed to touch anything they like, except possibly the One Ring.

    12. Re:Garlick and wooden stakes needed ... by Anonymous Coward · · Score: 0

      why would the Nazgul need Garlick(sic) and Wooden stakes?

      you must be young

    13. Re:Garlick and wooden stakes needed ... by ihtoit · · Score: 1

      So much this.

      --
      Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
  4. SCO actually got a bad deal here by Anonymous Coward · · Score: 0, Troll

    I certainly think the $699 and $1399 licensing fees were excessive. However, SCO was actually right about some things. I remember when SCO originally filed their lawsuit, saying their source code was illegally used in the Linux kernel. People called on SCO to indicate which files and lines of source code were their intellectual property. SCO actually showed their source code to analysts, who agreed that the Linux kernel contained the same code. Despite SCO actually publicly saying which files infringed upon their intellectual property, the response was a bunch of excuses. They claimed that SCO might not actually own the code they purchased from Novell. They claimed that the infringing code didn't count because copyright law couldn't protect it. The FOSS community moved the goalposts when SCO proved that Linux infringed upon their copyrights. Because they dared challenge IBM, a behemoth intent on making profits from Linux, they were run out of business. If you're big enough, have enough money, and buy enough lawyers, you can get away with anything. IBM is doing to SCO what Microsoft does to their opponents.

    1. 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.
    2. Re:SCO actually got a bad deal here by Anonymous Coward · · Score: 0

      Try explaining the nuances of software patents and software license violations to a judge and you're likely to get the same blank expression as you would explaining something to a particularly unintelligent dog. The courts will never "catch up" to technology because judges are mostly old folks who still use VCRs and don't quite understand that internet thing.

    3. Re:SCO actually got a bad deal here by 0xdeaddead · · Score: 1

      Yes yes, SGI sent in some 32v memory code, which was quickly tossed out.

      The joke being that 32v is free now, so it doesn't even matter.

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

      Apart from the fact that SCO NEVER owened the code they showed you're doing fine. Novel PROVED that they owened it and even got a judgement to show it.

    5. Re:SCO actually got a bad deal here by cheesybagel · · Score: 2

      The source code they pointed to was header files. You know POSIX API interface header files. Besides most of the claims they made had been shot down beforehand in the BSD/Unix lawsuit decades prior.

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

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

    8. Re:SCO actually got a bad deal here by mwvdlee · · Score: 1

      You wouldn't be saying such nonsense if you actually understood what source code is.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    9. Re:SCO actually got a bad deal here by Revek · · Score: 2

      https://yro.slashdot.org/story/03/12/22/2356243/linus-blasts-scos-header-claims
      They claimed basic header files.

    10. Re:SCO actually got a bad deal here by silentcoder · · Score: 2

      Of course the uncopyrightable nature of API's have irked many a corporation before, and seems to particularly irk them when Linux is involved in any way. Just look at the current Oracle/Google case over Java vs Dalvik.

      The sad reality is that crime and lawsuits are, by a massive margine, the largest profit centers there are - so pretty much every corporation ends up doing lots of both. Just making products customers want to buy will make you rich... but it won't make you THE RICHEST - and nothing less will do for the kind of people who run them.

      - One way to think about it: if all crime was done by one company, that company would make more money every year than the top 50 fortune 500 companies combined. Thats a massive percentage of the entire global GDP. There's absolutely no way all that money can be laundered unless two other things are true (it's literally mathematically impossible for them to be false):
      1) Every major corporation must be including a fairly significant chunk of that money in their annual earnings (where it already looks legitimate).
      2) Pretty much every large bank is complicite in the laundering of the rest. So when companies like HSBC get caught laundering money for terrorists, don't be shocked - they are not doing anything that every other bank wasn't doing as well - they just got caught.

      Of course the pretty sucky part of having damn near a quarter of all global profits made from crime is that crime has victims - but since nearly every single victim is poor, who cares about them right ?

      --
      Unicode killed the ASCII-art *
    11. 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.

    12. Re:SCO actually got a bad deal here by LWATCDR · · Score: 1

      Wow a wildly inappropriate comment and a wildly inappropriate reply.
      Couldn't you just have said, "stop being a bigot" and move on?

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    13. Re:SCO actually got a bad deal here by fnj · · Score: 1

      Mr. Daryl McBride

      Darl. DARL. His name is Darl, not Daryl. Jeeze.

    14. Re:SCO actually got a bad deal here by KGIII · · Score: 1

      It just so happens that I have a copy of the Linux kernel right here in front of me - oddly enough. As in, it's open in a folder and I've been looking at it. What, specifically, are these lines of code so that I might verify this for myself?

      --
      "So long and thanks for all the fish."
    15. Re:SCO actually got a bad deal here by Anonymous Coward · · Score: 0

      I'd say they've done a wonderful job at becoming a troll. They keep regenerating! We need a vat of boiling acid stat!

    16. Re:SCO actually got a bad deal here by Anonymous Coward · · Score: 0

      I just call him by my pet name... SCO Troll.

    17. Re:SCO actually got a bad deal here by mark-t · · Score: 1
      "Of course the uncopyrightable nature of API's have irked many a corporation before..."

      I see you haven't been following the Oracle vs Google case, since it's my understanding that the latest ruling on the matter determined exactly the opposite.

    18. Re:SCO actually got a bad deal here by cyberchondriac · · Score: 1

      "Hiah, Ah'm Darl, and this is mah other brother Daryl" ...

      --

      Look back up at my post, now look back down, you're on the Internet. Now look back up. I'm a signature.
    19. Re: SCO actually got a bad deal here by silentcoder · · Score: 1

      We cant mock bigots anymore ?

      --
      Unicode killed the ASCII-art *
    20. Re:SCO actually got a bad deal here by Anonymous Coward · · Score: 0

      which is a bigger problem because the straight idiots breed (rather more often in fact since they can't figure out how to use birth control).

      White peoples make up 8% of the world's population and their birth rates are in decline -- their populations actually fluctuate to maintain a stable equilibrium with nature at a comfortable population density rather than rape the earth by making babies they can't support when resources are scarce. So, white people aren't causing the over population problem. Therefore, if you want to hate on "breeders" then you're hating on brown and black and other non-white colored peoples. Congratulation, you're a racist Nazi.

      This has been a public service announcement from the SJW mind fuck department.

    21. Re: SCO actually got a bad deal here by LWATCDR · · Score: 1

      Simply wondering if the graphic nature off the mocking was needed. In fact I would say that the effectiveness of the mocking was decreased by the over the top reply.
      In other words you reply would not change anyone's mind and puts the original post in a less offensive light in comparison to your reply.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    22. Re:SCO actually got a bad deal here by Anonymous Coward · · Score: 0

      However, SCO was actually right about some things.

      There's only one suitable response: lol.

    23. 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.
    24. Re: SCO actually got a bad deal here by Anonymous Coward · · Score: 0

      We cant mock bigots anymore ?

      No, bigots are now classed as a protected minority.

    25. Re:SCO actually got a bad deal here by nikkipolya · · Score: 1
    26. Re:SCO actually got a bad deal here by ihtoit · · Score: 1

      SCO showed no such thing. No external analyst ever agreed any such thing. SCO never, not one time, showed a single line of code that they could legitimately claim ownership to that was in the mainstream Linux kernel. Which is why they LOST THEIR CASE.

      --
      Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
    27. Re: SCO actually got a bad deal here by ihtoit · · Score: 1

      problem is they're no longer a minority.

      --
      Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
    28. Re:SCO actually got a bad deal here by david_thornley · · Score: 1

      It determined that APIs are copyrightable. It rejected Google's interoperability argument on the grounds that Android and Java programs aren't actually interoperable, and that Google was copying the APIs for the convenience to Android programmers rather than to make things work in both environments, which means the interoperability defense wasn't tested. It said Google at least had an argument based on fair use, and sent that back to the district court to decide. The decision seemed very well-informed on technical matters.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    29. Re:SCO actually got a bad deal here by Insanity+Defense · · Score: 1

      JVM don't you have a Yahoo forum to troll or Wikipedia puppets to pretend aren't you? SCO lost and never owned the Unix copyrights, give it up.

  5. March 31 by ChunderDownunder · · Score: 4, Funny

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

    1. Re:March 31 by Anonymous Coward · · Score: 0

      It's all about ad revenue from click click clickity click.

    2. Re:March 31 by bug1 · · Score: 1

      No, i look forward to SCO suing microsoft as well, because they might have ported linux kernel code into windows as the screenshots of Microsoft/GNU/Linux BASH show.

    3. Re:March 31 by MrKaos · · Score: 1

      No, i look forward to SCO suing microsoft as well, because they might have ported linux kernel code into windows as the screenshots of Microsoft/GNU/Linux BASH show.

      Microsoft is one of SCO's shareholders, they have been funding SCO since the 80's. SCO is a proxy, so that the press is SCO vs IBM and I haven't seen anything that suggests Microsoft has exited the SCO board.

      --
      My ism, it's full of beliefs.
    4. Re:March 31 by Anonymous Coward · · Score: 0

      No, i look forward to SCO suing microsoft as well, because they might have ported linux kernel code into windows as the screenshots of Microsoft/GNU/Linux BASH show.

      Microsoft is one of SCO's shareholders, they have been funding SCO since the 80's. SCO is a proxy, so that the press is SCO vs IBM and I haven't seen anything that suggests Microsoft has exited the SCO board.

      Sorry, you get a failing grade in History, but an A+ in dumbassery.

      The company currently calling itself SCO is an imposter that has only existed since 2001.

      The Santa Cruz Operation (the original SCO) was founded in 1979 and then sold its UNIX business to Caldera in 2001. After that sale, SCO changed its name to Tarantella and Caldera then changed its name to The SCO Group.

      Caldera, now calling itself SCO, began pretending to be the original SCO. For example, in 2004 proclaiming "our 25th anniversary" despite the fact that Caldera was only founded on 1994.

    5. Re:March 31 by Anonymous Coward · · Score: 0

      Maybe the submitter is Australian?

    6. Re: March 31 by Anonymous Coward · · Score: 0

      Not yet, it is now Tomorrow in kiwiland though

    7. Re:March 31 by Teun · · Score: 2, Insightful

      The licensing was taken care of, Miscrosoft purchased legal protection from SCO for their UNIX tool-kit for windows,.

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    8. Re:March 31 by silentcoder · · Score: 3, Informative

      Microsoft was basically the only company to buy a "unix license for linux" from SCO back in the day (mostly to keep the fight going and undermine their competition) so suing them now would be idiotic even by SCO standards. Don't bite the hand that fed you and all that.

      --
      Unicode killed the ASCII-art *
    9. Re:March 31 by MrKaos · · Score: 1

      Sorry, you get a failing grade in History, but an A+ in dumbassery.

      Maybe I can get some pointers from you in Assholery, it looks like you topped that class.

      The company currently calling itself SCO is an imposter that has only existed since 2001.

      The Santa Cruz Operation (the original SCO) was founded in 1979 and then sold its UNIX business to Caldera in 2001. After that sale, SCO changed its name to Tarantella and Caldera then changed its name to The SCO Group.

      Caldera, now calling itself SCO, began pretending to be the original SCO. For example, in 2004 proclaiming "our 25th anniversary" despite the fact that Caldera was only founded on 1994.

      Ok, so who's on the board then?

      --
      My ism, it's full of beliefs.
    10. Re:March 31 by bug1 · · Score: 1

      Nothing is idiotic on April fools day, apparently

    11. Re:March 31 by Anonymous Coward · · Score: 0

      When there is no food, the hand that fed you is made of meat, and is the closest thing you've got.

    12. Re:March 31 by Anonymous Coward · · Score: 0

      Sun also. They licensed because, well they were Sun and did everything stupid.

    13. Re:March 31 by Anonymous Coward · · Score: 0

      > Microsoft is one of SCO's shareholders,

      MS became a shareholder when they sold Xenix to the Santa Cruz Operation. Paul Allen was on the board at that time. In the 90s MS sold all those shares and Paul left SCO.

      > they have been funding SCO since the 80's.

      SCO made payments to MS for code in Xenix/Open Server but had replaced all that code and had a court repudiate that part of the contract. MS did not 'fund' SCO in the 80s or 90s.

      > SCO is a proxy, so that the press is SCO vs IBM and I haven't seen anything that suggests Microsoft has exited the SCO board.

      The original SCO sold the Unix business to Caldera which renamed itself The SCO Group. This has nothing to do with the original SCO nor with Microsoft. In fact The SCO Group sold the litigation rights to another bunch of scumbags, so it is not them either.

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

    Who is funding the appeals at this point?

    1. Re:Follow the money by gtall · · Score: 1

      The lawyers are on autopilot due to their agreement to continue to proceed long after reason and/ior the death of SCO. Their paralegals are working overtime during coffee breaks to file these appeals.

    2. Re:Follow the money by Anonymous Coward · · Score: 0

      Probably some of the trillions of cash idling in VC and corporate vaults. Negative real interest rates might actually make taking a flier on a possible multi-billion-dollar award worth the several million $ investment it'll require to keep the case shambling along.

      Capitalism!!! Patents!!!

    3. Re:Follow the money by ThatsNotPudding · · Score: 1

      Who is funding the appeals at this point?

      Probably a certain NBA team.

    4. Re:Follow the money by Anonymous Coward · · Score: 0

      Exactly, it's probably at least as good a risk/reward ratio as funding tech startups hoping for a unicorn. Maybe better.

    5. Re:Follow the money by StormReaver · · Score: 2, Interesting

      The sleezy law firm representing SCO and Oracle contracted with SCO to represent them through all appeals for the up-front payment of $20M that SCO paid.

    6. Re:Follow the money by RogueWarrior65 · · Score: 1

      Came here to ask this question. Trial lawyers don't work for free. Somebody has to be paying them to keep working on this. My guess is that it's a long con. SCO figures that Linux is EVERYWHERE and will reach even further with IoT so if they can win a court case, they can go after license fees till the cows come home.

    7. Re:Follow the money by whoever57 · · Score: 1

      1. Lawyers have been paid up front, including appeals.
      2. None of the remaining claims affect Linux, they are contract claims against IBM. At this point, even if IBM lost, SCO could not get license fees for Linux usage.

      --
      The real "Libtards" are the Libertarians!
    8. Re:Follow the money by StormReaver · · Score: 1

      I should also add that SCO paid its attorney fees with Novell's money.

  7. Covering Asses by nateman1352 · · Score: 1

    At this point they are probably just trying to prevent SCO's former shareholders from suing McBride and his cronies for professional negligence.

  8. Now-defunct Unix vendor... by Anonymous Coward · · Score: 0

    No, SCO was called Caldera, a Linux vendor who bought a failing, minor UNIX for PC shop. Period.

    1. Re:Now-defunct Unix vendor... by Lisias · · Score: 1

      no.

      SCO, Santa Cruz Operation, was an UNIX vendor. They bought XENIX from Microsoft and rebranded it as SCO Unix.

      --
      Lisias@Earth.SolarSystem.OrionArm.MilkyWay.Local.Virgo.Universe.org
    2. Re: Now-defunct Unix vendor... by Anonymous Coward · · Score: 0

      Current SCO has nothing (not much) to do with Santa Cruz Operation. They changed name from Caldera to SCO (and later to 'the SCO group') after they started this sorry affair.
      They did this exactly to create confusion about who they were.

      More info about this in the second paragraph on the Wikipedia page:
      https://en.m.wikipedia.org/wiki/Santa_Cruz_Operation

    3. Re:Now-defunct Unix vendor... by Anonymous Coward · · Score: 1

      Nope. Santa Cruz Operation sold of it's unix to Caldera, rebranded itself as tarantella inc. Caldera rebranded as the SCO we know and love.

    4. Re:Now-defunct Unix vendor... by drinkypoo · · Score: 1

      SCO, Santa Cruz Operation, was an UNIX vendor. They bought XENIX from Microsoft and rebranded it as SCO Unix.

      No. SCO, Santa Cruz Operation, was a UNIX vendor. They bought XENIX from Microsoft and rebranded it as SCO XENIX. They maintained this product line separately from their UNIX line. It did less, and they sold it for less money. It would, however, run on a 286. I used to have a 286-6 with 1MB of RAM and a 40MB Seizegate RLL disk running Xenix 2.3.2 as a UUCP node.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    5. Re:Now-defunct Unix vendor... by Gr8Apes · · Score: 1

      Xenix, IIRC, was a reason Windows 3.0 succeeded. That thing just wouldn't run anything.

      --
      The cesspool just got a check and balance.
  9. Darl McBride is a waste of breath by Anonymous Coward · · Score: 0

    There's no point in suing that worthless sack of waste material. All he's really doing is kidding himself about it all.

    The only thing worth mentioning about this whole case is that it adds yet another nail to the coffin of assuming that you can force your way onto others with intimidation. Only a truly worthless fool believes in such methods.

    1. Re:Darl McBride is a waste of breath by Anonymous Coward · · Score: 0

      I mean seriously his name is Darl. That's like something a neanderthal would come up with, furtively trying to make comprehensive new sounds. Other than Darl McBride who have you ever heard of named Darl? No one, that's who. It would be like naming your kid Pyle instead of Kyle and wondering, why does everyone call him Gomer?

      Darl, the man so retarded, even his name sounds retarded. And his view of the history of Unix is extremely retarded.

      I miss PJ and Groklaw.

    2. Re:Darl McBride is a waste of breath by ihtoit · · Score: 1

      Groklaw rocked. Whatever happened to PJ?

      --
      Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
  10. Freddy Kreuger to SCO by jargonburn · · Score: 1

    "Why won't you DIE?"

  11. What will it take for SCO to die? by Anonymous Coward · · Score: 0

    I recommend a stake thru the heart...

    1. Re:What will it take for SCO to die? by Anonymous Coward · · Score: 0

      Sorry, no heart to stake in that one..

  12. They don't want to get on the cart. by Anonymous Coward · · Score: 0

    Get on the fucking cart, SCO. You're diseased.

  13. Court document on groklaw.net by bartjan · · Score: 2
    1. Re:Court document on groklaw.net by Anonymous Coward · · Score: 0

      Which tells us nothing at all. In particular, it doesn't set out the grounds for appeal.

    2. Re:Court document on groklaw.net by Anonymous Coward · · Score: 0

      I still miss all the good coverage Groklaw used to provide on cases like this and with Oracle Vs. Google. Is there anybody who has seriously taken up the task at least half as well?

  14. US Justice System Failure by Anonymous Coward · · Score: 0

    This case is the embodiment of everything that is wrong with the US justice system. If anyone needs any more evidence that it's time to just completely start again, the fact that this utter crap has been allowed to drag on for something like 13-odd years is it.

    1. Re:US Justice System Failure by Anonymous Coward · · Score: 0

      > This case is the embodiment of everything that is wrong with the US justice system.
      > If anyone needs any more evidence that it's time to just completely start again, the
      > fact that this utter crap has been allowed to drag on for something like 13-odd years is it.

      Gowachin law, anyone? *hefts spear*

    2. Re:US Justice System Failure by mikael · · Score: 2

      It was funded by various other OS vendors to create FUD to slow down the adoption of Linux.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    3. Re:US Justice System Failure by Anonymous Coward · · Score: 1

      Specifically Microsoft and Sun.

    4. Re:US Justice System Failure by rudy_wayne · · Score: 1

      This case is the embodiment of everything that is wrong with the US justice system. If anyone needs any more evidence that it's time to just completely start again, the fact that this utter crap has been allowed to drag on for something like 13-odd years is it.

      I followed the case for a while and I was quite shocked by the complete corruption and incompetence of the various federal judges involved. Over and over again they allowed SCO to play ridiculous games in order to keep their case alive.

    5. Re:US Justice System Failure by silentcoder · · Score: 1

      Some of the little boys who were born on the day this case was filed have had their first wet dreams by now - and still it drags on.

      --
      Unicode killed the ASCII-art *
    6. Re:US Justice System Failure by Anonymous Coward · · Score: 1

      You have it all Wrong - in the U.S. we have a LEGAL SYSTEM, NOT a Justice System!!

  15. SCO had minimal resources due to SCO's bankruptcy. by Anonymous Coward · · Score: 0

    Duh. I once asked an executive why they didn't sue another company who had given them grief. Executive said it's a good way to waste your employee's time and your company's money. He said suing isn't a good business plan. SCO should have listened.

    They must have long gone but founders Doug Michels and Larry Michels must cringe everytime they hear someone mention SCO.

  16. Why is it possible to keep doing this? by Anonymous Coward · · Score: 1

    Isn't this harassment or something?
    Isn't there some point where if the courts have ruled against you several times it's over?
    Or can you just keep doing this forever as long as you can pay a lawyer?

    1. Re:Why is it possible to keep doing this? by Anonymous Coward · · Score: 0

      Isn't this harassment or something?
      Isn't there some point where if the courts have ruled against you several times it's over?
      Or can you just keep doing this forever as long as you can pay a lawyer?

      As long as there is a legitimate avenue of appeal available, you have the right to appeal. Yes, SCO is a bunch of scumbags who should have died a long time ago, but legally, they have the right to do it.

    2. Re:Why is it possible to keep doing this? by bluefoxlucid · · Score: 1

      Legal barratry. If dismissed with prejudice, it means they're no longer allowed to do this. Dismissal with prejudice means this case is over and can no longer come to court.

    3. Re:Why is it possible to keep doing this? by Anonymous Coward · · Score: 0

      > Why is it possible to keep doing this?

      Not possible, but necessary. Because of honour. SCO was Unix before Linus was a mere indecent thought. They know they are right, Linux was blatant theft and IBM, which racketeered off Linux, needs to pay weregild. They will go on, until all legal venues an exhausted and if still wronged, they will act like a corsican or sicilian manly MAN would. In the 22th century classical operas will be written and performed on the stage, where the wronged SCO executive executes the morally corrupt IBM bosses in the end and proudly displays his bloodied stiletto in the streets. It will be titled Linux of Lammermoor or whatever.

    4. Re:Why is it possible to keep doing this? by Todd+Knarr · · Score: 1

      They can, however, unfortunately appeal the dismissal with prejudice, which is probably what they're doing. The appeal will probably result in a one-line rejection, but it delays the inevitable for them by another few weeks while the appeals court processes the paperwork.

    5. Re: Why is it possible to keep doing this? by Anonymous Coward · · Score: 0

      Take your pills with a glass of water, not undiluted Coca-Cola syrup ...

  17. The Turd That Won't Flush by Anonymous Coward · · Score: 3, Funny

    SCO is like a turd that won't flush. No matter how many times you bury it in paperwork, just when you think it's finally gone ... then it comes bubbling up again.

  18. Seriously by Quzak · · Score: 1

    Just fucking die already SCO. FFS

    --
    Support your local school shooter, give them your firearms.
  19. The question now is: Microsoft money? by Anonymous Coward · · Score: 0

    We know from history (see e.g.[1]) that this useless lawsuit was partly fueled by Microsoft money, most likely trying to harm the free software "ecosystem".

    The question, now that Microsoft is getting all cuddly with "Linux" is... is still any Microsoft money powering the zombie?

    Darn. How I miss Pamela Jones.

    [1] https://en.wikipedia.org/wiki/...

    1. Re:The question now is: Microsoft money? by mikael · · Score: 1

      Remember "Embrace , Extend, Extinguish" and "Developers, Developers, Developers".

      Microsoft just needs to pull off those developers with new ideas from Linux to Windows.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    2. Re:The question now is: Microsoft money? by JustBoo · · Score: 1

      Remember "Embrace , Extend, Extinguish" and "Developers, Developers, Developers".

      Microsoft just needs to pull off those developers with new ideas from Linux to Windows.

      Bingo! I wish I had mod points. If anyone thinks Microsoft has fundamentally changed, they are in for a big surprise.

      Microsoft's persona is no longer that sweaty coke-fueled guy throwing chairs. It's now the kindly Grandma coming up and offering sweets, then when you are distracted, she sticks a stiletto in your back and twists, and smiles as she watches the life drain from your eyes. EEE indeed.

  20. Here we go again! by some+old+guy · · Score: 2

    If it doesn't get summarily dismissed (highly likely) and becomes as entertaining as Caldera v. IBM, I wonder if pj will resurrect Groklaw.

    --
    Scruting the inscrutable for over 50 years.
  21. April Fool! by GrahamCox · · Score: 1

    Surely. Has to be. Hasn't it?

  22. D state, waiting for kernel (often blocking io) by raymorris · · Score: 1

    Those will show D state in ps, indicating that the process is waiting on the kernel. Frequently it's waiting for blocking io - it has asked the kernel for some disk block and won't do anything else until the kernel wakes it up when the data is available. The program code itself isn't running on the cpu at this point, the kernel code is (and the kernel thread may be deadlocked).

    I helped fix such an issue related to LVM on top of RAID1, where it was possible for LVM the lvm layer to be waiting on the raid layer, while the raid layer was waiting on the LVM layer.

    Recent (two years ago?) kernels handle D state processes better.

    1. Re:D state, waiting for kernel (often blocking io) by PetiePooo · · Score: 1

      Funny you mentioned this. I was recently using Intel software raid (isw, aka fakeraid) to mirror my root flash drives. Big mistake! The dmraid package, on closer inspection, says, "DO NOT USE; Not production quality." The flash drives would hiccup (still don't know why) and "sort of" drop out of the RAID. I say sort of because, near as I could figure, they'd completely stop responding to IO, but the kernel would still queue IP calls to them. I'd end up with a slew of processes in state D, mostly cron, and if I didn't catch it in time, it would fill the process table with them.

      It was weird in that, often I could still ssh to the machine and run some programs, but anything that pulled lots of blocks from root or try to flush to root would go into state D and never return. That includes, oh, shutdown, reboot, init, and the like... :( I was able to load an IPMI utility and tell the PMU to reset the system, though, and it would come up like nothing ever happened.

      The solution was to delete the RAID metadata block and reboot, which switched the root mount to the underlying device instead of the devicemapper. No more RAID, but no more strange diskIO issues either. With a little resize2fs and fdisk magic, I could then repartition the non-used mirror drive as an mdadm mirror, reboot onto it and sync to the other to regain my redundancy.

      Good times!

  23. PS use killable IO and locks to prevent this by raymorris · · Score: 1

    One way to prevent this is to use KILLABLE system calls instead of blocking ones. The _killable versions block just like blocking mode, but they allow kill -9 to work. The userspace program doesn't have to worry about handling half-completed io, because it dies without passing go.

  24. What if? by Anonymous Coward · · Score: 0

    What if SCO is right and IBM is the big bad exploiter here? What if using Linux is morally wrong?

    1. Re:What if? by Anonymous Coward · · Score: 0

      You're correct, it is like that. But who is to say that God is a peacefully loving guy, and isn't actually a raping pedophile?

      Just because the question is aligned with your believes, it isn't an invalid or preposterous question

    2. Re:What if? by armanox · · Score: 1

      Then SCO can provide some evidence that IBM did infringe on code that they own, which they have failed to do to date. And should they be able to show that code is infringing, the Linux community will alter the code so that it no longer infringes. But like I said, SCO first needs to show that code was copied, and that it was copied from them (the last time they provided code that was BSD licensed).

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
    3. Re:What if? by Eunuchswear · · Score: 2

      The joke is that the original claims from Caldera had some truth. It's just that someone went insane and thought they could sick up IBM for money.

      If you go back to the very beginning you'll find that what was happening was that some unscrupulous consultants were porting applications from SCO UNIX to Linux by copying the SCO shared libraries to Linux systems without a license. Somehow, by a convoluted system of chinese whispers this got misunderstood as "Linux contains UNIX code", and some crazy person at Caldera's eyes lit up with flashing dollar signs.

      And the rest is hysteria.

      --
      Watch this Heartland Institute video
    4. Re:What if? by Anonymous Coward · · Score: 0

      They probably saw the $9B+ claim from oracle and APIs and are going to say linux copied their header files is the same thing and that they should get the moneys?

    5. Re:What if? by halivar · · Score: 1

      Other way around. Caldera/SCO was copying Linux code into Unix for their Linux Kernel Personality project. This was their "smoking gun" that got dropped like a hot potato.

    6. Re:What if? by Eunuchswear · · Score: 1

      No, I'm not talking about copying source code.

      I'm literally talking about some fly by night "consultant" copying /usr/lib/libc.so.1 from a UNIX system to a Linux system so that their crappy app written for SCO UNIX could be run on Linux.

      This actually happened. Go look at the very first filings from TSCOG and you'll see that that was what they were first complaining about.

      But then they went mad.

      --
      Watch this Heartland Institute video
    7. Re:What if? by halivar · · Score: 1

      That exact file you mention is part of the OpenServer LKP, and contained Linux code SCO/Caldera had no right to distribute outside the GPL.

    8. Re:What if? by Eunuchswear · · Score: 1

      No it isn't. It's the C library.

      --
      Watch this Heartland Institute video
  25. time for Tagon's Toughs by ct_zero_interupt · · Score: 0

    http://schlockmercenary.wikia.com/wiki/Partnership_Collective/
    The Partnership Collective is the galaxy's largest law firm, consisting of a single huge hivemind. The Collective is represented by its army of snakelike "attorney drones", which it clones by the millions. The hivemind's personality is a stereotypical slimy lawyer writ large, with attorney drones at one point seen gleefully celebrating a bus crash as an opportunity for litigation.

    The Partnership Collective was used as a catspaw by the F'sherl-Ganni to attack Tagon's Toughs, in hopes of eliminating them before they could release the teraport. They made several attacks on the Toughs, including calling KFDA commandos on them, launching a kinetic missile attack, and attempting to assimilate Massey Reynstein, a public defender representing one of the Toughs. Their final try was planting obscenely overpowered bombs on the Toughs' ship, powerful enough to have caused worldwide damage on Luna had they gone off as planned. (One wonders where they even found bombs that big, let alone why they thought it wise to use them.)

    After the bombing attempt, the Luna government sentenced the Collective to the destruction of one million of its expensive attorney drones. Reynstein, now working for Tagon's Toughs, convinced the court to make the Toughs the agents of this penalty, giving them near-perpetual license to kill Collective drones on sight and get paid for it. As a result, the Collective began avoiding the Toughs like the plague, and since the Collective is nearly ubiquitous, legal opponents of the Toughs tended to find themselves suddenly lawyerless.

    --
    Mal's Content http://malcontent.malcolmcampbell.org
  26. SCO is unreliably, deniably dead by Lotus456 · · Score: 2

    I know, didn't we just have a funeral for these clowns?

    https://yro.slashdot.org/story/16/03/01/154214/sco-is-undeniably-reliably-dead

    --
    "It's a good computer... for I to BM on!" - apologies to Triumph, the insult comic dog
  27. "judgment", not "judgement" by Anonymous Coward · · Score: 0

    This is 'Merica.

  28. Whew... by 110010001000 · · Score: 1

    Now I am glad I paid my $699 license fee to SCO.

    1. Re:Whew... by Anonymous Coward · · Score: 0

      Now I am glad I paid my $699 license fee to SCO.

      I wish I had bought one. I am sure a Linux license from SCO will be a collector's item and will go for like a million dollars some day.

  29. SCO is now Xinuos ? by Anonymous Coward · · Score: 0

    www.sco.com redirects to www.xinuos.com
    They still offer "SCO OpenServer®" alongside their new "Xinuos OpenServer 10".

    1. Re:SCO is now Xinuos ? by Eunuchswear · · Score: 2

      No, TSCOG is still TSCOG, bankrupt.

      They sold SCO UNIX and UnixWare to Xinuos.

      --
      Watch this Heartland Institute video
  30. Just like the Rocky and Bullwinkle show... again!! by MegOnWheels · · Score: 1

    Wow first the recent resurrection of the crypto escrow / back door arguments by various governments and now SCO have sadly returned from the dead to try and eat brains again.

  31. They real way to kill a zombie process... by SadButResolved · · Score: 1

    https://www.cs.unm.edu/~dlchao... Or perhaps Microsoft Azure sales guys can stop them? We love Linux!!!!

  32. Prepare to vi... by Anonymous Coward · · Score: 0

    Sorry.

  33. Re:Zombie (the "d" in systemd) by Provocateur · · Score: 2

    The d in systemd stands for defunct, as originally intended.

    The court case will determine if it stands for "die, already"

    The planets are in alignment. Slashdot will be forced to print a dupe of a 13 year old story, on April Fool's Day no less, which triggers a fresh 13-year cycle of dupes that really aren't. And we have SCO to thank. Whodathunkit?

    --
    WARNING: Smartphones have side effects--most of them undocumented.
  34. Re:Requests to Slashdot's Management by Anonymous Coward · · Score: 0

    Though I agree with your sentiment, I had to mod you offtopic as this is not the right place to post this. Sorry.

    -TheReaperD

  35. Re:SCO had minimal resources due to SCO's bankrupt by Eunuchswear · · Score: 1

    Duh. I once asked an executive why they didn't sue another company who had given them grief. Executive said it's a good way to waste your employee's time and your company's money. He said suing isn't a good business plan. SCO should have listened.

    Oh, SCO listened. That's why they sold their rights to sell UNIX to Caldera.

    They must have long gone but founders Doug Michels and Larry Michels must cringe everytime they hear someone mention SCO.

    Doug and Larry have nothing to do with TSCOG.

    --
    Watch this Heartland Institute video
  36. Like criminals filing frivolous suits from jail by Anonymous Coward · · Score: 0

    These people are like criminals filing frivolous suits from jail. They lose nothing by doing so and could have a big gain, a version of the "legal lottery". Losses and sanctions are incurred by the legal construct that is the company, not the individuals doing the harassment.

    The way to stop this is to actually go after the individuals behind this, not to beat up on the construct/company they hide behind.

  37. Re:Requests to Slashdot's Management by tom229 · · Score: 2

    After all that, fix the God damned mobile site. My slashdotting is entirely done on my phone using the desktop interface. Not because I dislike the mobile interface look, but because it lacks similar functionality. Minor things like not being able to collapse comments makes it almost unusable. The first rule of mobile interfaces is they need to have the same functionality as the desktop. It's no surprise the hipsters at dice didn't know this. Now let's move forward.

    --
    If it ain't broke, don't fix it.
  38. snowdon, detective, groklaw... by Midnight+Thunder · · Score: 1

    The first point here is to figure out the individuals behind this and who's sponsoring them. Then publish who they are and see if they still are interested in pursuing the matter.

    Does Snowdon not have any files on this entity? Next bet it we sponsor the EFF to hire a private detective to do an investigation to the finances of flow of money to this entity? Also wondering whether this will be story enough to revive Groklaw?

    --
    Jumpstart the tartan drive.
  39. SCO on agonal breathing now by Anonymous Coward · · Score: 0

    Everything dead except the brain taking desperatly ineffective breaths to get oxygen

  40. OT, sorry by JazzLad · · Score: 1

    Ping me via email unless you can guess why I'm asking you to ping me :)

    --
    "If you have nothing to hide, you have nothing to fear." - Every fascist, ever
    1. Re:OT, sorry by KGIII · · Score: 1

      LOL I don't know what did it yet - but they've got logs showing the CPU spiked out of control so I've gotta figure that out. They'll let me back in tomorrow morning. ;-)

      --
      "So long and thanks for all the fish."
  41. SCO being funded by LA Clippers? by Anonymous Coward · · Score: 0

    or is it being funded by Intellectual Vultures. Hey, it ain't /. unless we find the paws of Microsoft stuck into something tied to GNU/Linux.

  42. Fun. mdadm indeed by raymorris · · Score: 1

    > I was recently using Intel software raid (isw, aka fakeraid) to mirror my root flash drives. Big mistake! The dmraid package ...

    Indeed. I tried out all the different kinds of RAID and settled on mdadm. Hardware RAID is handy if you're using a CPU from 1999 and also don't need any flexibility. LVM mirrors are a handy way to make a one-time copy of data.

  43. 13 Years Later, we find out What SCO Really Means by Provocateur · · Score: 1

    SCOuting for money

    de-defunct

    It happens to be April 1 somewhere where SCO's lawyers are hiding; we're reading tomorrow's news for nerds today.

    --
    WARNING: Smartphones have side effects--most of them undocumented.
  44. Not dead yet! by Anonymous Coward · · Score: 0

    But I'm not dead yet, in fact I think I'm feeling better.

  45. Inflation by Hognoxious · · Score: 1

    Can anybody tell me what - after adjusting for inflation - the current value of a cock-smoking teabagger is?

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  46. April Fools Day is tomorrow! by anegg · · Score: 1

    Please let this be an early April Fools Day joke.

  47. kill -9 SCO by swschrad · · Score: 1

    dayamn, some fool keeps restarting it. what terminal are they on? -- send a guy with a sledge down there.

    --
    if this is supposed to be a new economy, how come they still want my old fashioned money?
  48. Memories, pressed between the pages of my mind... by GrumpySteen · · Score: 1

    Just 30 days ago... SCO Is Undeniably, Reliably Dead.

  49. Dun dun, dun di-duhn. by twotacocombo · · Score: 1

    Listen, and understand! That SCO is out there! It can't be bargained with. It can't be reasoned with. It doesn't feel pity, or remorse, or fear. And it absolutely will not stop, ever, until...?

  50. Re:Requests to Slashdot's Management by Anonymous Coward · · Score: 0

    -1, irrelevant to the article
    +50, agree

  51. Re:Requests to Slashdot's Management by hankwang · · Score: 1

    http://avantslash.org/ - I browse slashdot nearly exclusively using this mobile interface, especially while commuting. Main downside: you need to host it as a script on your own server.

  52. Come back to us, PJ by Anonymous Coward · · Score: 0

    We miss you.