Slashdot Mirror


IBM Files for Partial Summary Judgement vs SCO

Armchair Dissident writes "The Register is reporting that IBM has filed for partial summary judgement against SCO. Groklaw also has the story, and is saying that SCO was still offering the disputed code for download as recently as August 4 2004. If this is true, then - according to Groklaw - SCO's case must surely be scuppered. Again."

98 of 367 comments (clear)

  1. Don't be so cheap, everyone by Bring+back+the+old+t · · Score: 2, Funny

    Pay your $699 fee, and shut up!

    1. Re:Don't be so cheap, everyone by Xenographic · · Score: 5, Informative

      Didn't you read? They're planning to raise their prices.

      Anyhow, I submitted something just like this, only with about a dozen links to more information (sadly, I don't have all of them here now), so perhaps I can explain more --

      This motion follows IBM's motion to strike Sontag's declaration as incompetant (he doesn't know jack about IBM's internal source controls, but he made a number of wild guesses and swore to them under oath), as well as IBM's movement for a declaration of non-infringement concerning their Linux activities. It is ironic on the last part that SCO doesn't want to let them have one, and it says at the same time that they're not arguing that IBM has infringed on their copyrights now.

      I'd link those motions, but I don't have time. They can all be found on Groklaw's legal documents page. Just be sure you're looking at the SCO vs. IBM part, and that you start at the bottom & scroll up--both SCO's complaint & IBM's counter-claims have changed over time, and you want the most recent version.

      If they were to grant all of IBM's motions, they would be enough to rend pretty much all Linux-related issues from this case, and would leave SCO with almost nothing that could stand on its own and SCO would still face the counter-claims.

      Of course, the judge has to be really strict on granting summary judgements. There have to be no material (relevant) issues of fact to decide--the evidence has to be so one-sided that no rational trier of fact could possibly decide for SCO on any of the issues the judge decides. This is important because the judge rules on the law, while the jury rules on the facts in any jury trial. If you can't guess from that, a summary judgement is where the judge gets to decide an issue early because there are no material issues of fact for a jury to decide.

      In other words, though IBM's motions are well-argued, they face a *very* high standard of law here. Please note that while Enderle has said that he would decide for SCO, that's irrelevant because the trier of fact would have to be rational, and logic is not Enderle's strong suit.

  2. Even if they offer a "download" by Anonymous Coward · · Score: 2, Interesting

    Even if they offer a "download" of the disputed code, how do we know they didn't just copy some random code which did exist in the kernel?

    1. Re:Even if they offer a "download" by meringuoid · · Score: 5, Informative
      Even if they offer a "download" of the disputed code, how do we know they didn't just copy some random code which did exist in the kernel?

      If they offered their disputed code for download as part of SCO Linux, then they put it under the GPL themselves.

      Their get-out for this is 'we didn't know our code was in Linux!', which might have been a case for them... if they didn't carry on making Linux available after they supposedly discovered their code in it.

      By leaving SCO Linux available for download under the GPL after they knew their alleged property was in it, they've GPL'd that property. Hence, they're stuffed.

      --
      Real Daleks don't climb stairs - they level the building.
    2. Re:Even if they offer a "download" by minotaurcomputing · · Score: 2, Funny

      "how do we know they didn't just copy some random code which did exist in the kernel?"

      I guess we'll just have to take their word for it.

    3. Re:Even if they offer a "download" by albalbo · · Score: 4, Informative

      I don't think it's necessarily the case that the code becomes GPL'd by default - although that argument could be made - just that by continuing to make it available, other people can have a reasonable expection that the code is OK. It's called estoppel, and it basically means that their past behaviour would stop them from suing people.

      --
      "Elmo knows where you live!" - The Simpsons
    4. Re:Even if they offer a "download" by ajs · · Score: 5, Informative

      And they did offer it for download for a LONG time. Many people, myself included, were posting links to the kernel source RPM on their ftp site for the first 6 months or so of the suits, here on Slashdot. I have a downloaded copy of it.

      It was the 2.4.13 kernel with some patches, so if AND ONLY IF, SCO has a problem with code that was added after 2.4.13, can they really mount a case that that code was not put under the GPL by SCO after the suit began.

    5. Re:Even if they offer a "download" by Scarblac · · Score: 4, Interesting

      Well, they claim it is their code, it is downloadable from their website, as their product "SCO Linux", under the GPL. If that doesn't make the code in question released under the GPL, I don't know what does.

      --
      I believe posters are recognized by their sig. So I made one.
    6. Re:Even if they offer a "download" by eric76 · · Score: 4, Insightful

      Assuming for the sake of argument that SCO really did own the rights to the code, if they did not wish to distribute the code under the GPL, they would necessarily have to cease distributing the code when it was discovered.

      SCO's continued knowing distribution of the code under the GPL should clearly indicate their acceptance and intention to do so.

    7. Re:Even if they offer a "download" by CmdrGravy · · Score: 3, Insightful

      They are saying that IBM have taken some of SCO's code and then ( somehow ) been inspired by that to write AIX etc which they then used to improve Linux.

      By selling or giving away there own version of Linux which incorporates the improvements made by IBM SCO are saying that on the one hand IBM has ruined there business by improving Linux but on the other hand that they are happy to sell, give away and work with the version of Linux which has ruined there business and that I think is a slightly ridiculous point of view to take.

    8. Re:Even if they offer a "download" by bobetov · · Score: 5, Funny

      I've been wondering why they haven't taken down the code from their servers. It just occurred to me that they may not have anyone in their company left who knows *how* to.

      --
      Looking for a Rails developer in Chapel Hill?
    9. Re:Even if they offer a "download" by bloggins02 · · Score: 5, Insightful

      Actually, this is not the argument given in the Request for Partial Summary Judgement (and yes, I read the whole thing, I was bored last night).

      The argument given by IBM is that SCO cannot on the one hand sue IBM for breach of contract and damage done by said breach and on the other hand knowingly continue to offer (and through advertising, tout the benefits of) the "offending" code in question.

      The key word here is knowingly. IBM claims (and I think claims correctly), that since the code (Kernel 2.4) is still available on their website after they knew about it, SCO waives their right to sue for breach of contract on the code in question.

      If the judge agrees, then game over for SCO.

    10. Re:Even if they offer a "download" by Waffle+Iron · · Score: 3, Interesting
      The real question is that can SCO recall its copyright. Just because it offered the code does it preclude it from unoffering it. They can not sue people who have THAT code but can say that derivative works are illegal if there was such a clause in their license, which it seems there was.

      However, in addition to their proprietary license, they chose to offer THAT code under a license, the GPL, that allows the recipients to recursively redistribute it. Since they still offer it, they have done this knowingly. SCO (or more likely, Novell) might retain a copyright on some code, but the terms of that license specify that it can't be "unoffered" from any recipients. These recipients may in turn redistribute it as they please.

      In the worst case, IBM would just have to download the Linux code again from SCO's public FTP server and run a script to pointlessly replace any identical strings of text in IBM's kernel sources from SCO's source files.

    11. Re:Even if they offer a "download" by Steve+Franklin · · Score: 2, Interesting

      "A good analogy would be the trial of Sadam Hussien. When he was put on the stand he declared the invasion to his country illegal and asked the judge under whose authority he was being tried."

      I strongly suspect the problem with Saddam's argument is that international relations are pretty much anarchical. There is no world government per se. There are treaties that forbid invasions, but as we have seen, they are not worth the toilet paper they are printed on. In this arena, might still makes right. What is disgusting about the whole affair is the mockery it makes of a judicial process based on non-existent law. To use the form of law to punish someone who is guilty of annoying the powers that be in Washington is a joke. They just don't have the nerve to act like the Imperial force they obviously think they are.

      How does this relate to SCO? In one quite basic way. SCO is using the form of the law to try to intimidate and even blackmail people when they have no legal position at all. They are, in short, megalomaniacal to the point of transferring the methods of national aggression to the field of commercial relations, where they are virtually unarmed.

      --
      Hic iacet Arthurus, rex quondam rexque futurus.
    12. Re:Even if they offer a "download" by slipstick · · Score: 4, Insightful

      As IBM's motion clearly points out it's called "waiver". By knowingly distributing the code under the GPL, SCO has waived all claims against IBM(and anyone else) for any code that might be in Linux illegally(I say might because I think the whole idea is a sham).

      Anyway, basically SCO can't sue someone else for the same action they are in fact performing.

      --
      Sure information wants to be free, but how much are you willing to pay for the packaging?
    13. Re:Even if they offer a "download" by frp001 · · Score: 2, Interesting

      So... If you are distributing somehting under a license which is invalid. What does this mean?

      --
      May I use your sig please?
    14. Re:Even if they offer a "download" by hhawk · · Score: 2, Interesting

      Why can't SCO Claim.

      1) we didn't know it was there
      2) Once we found out it was released everywhere by IBM the horse was way out of the barn.
      3) IBM'S "illegal" actions have boosted the Linux market place
      4) To stay competitive we have to release a copy of Linux, under GPL, to be competitive.
      5) But all of this is a result of the fruit of IBM's "illegal" actions so they still owe us damages.

      What I don't understand is how they can try to sell Linux lic. when their own vers. of Linux is available under GPL; that opens the door for it to go into every other linux copy legallly (assuming (even) it was there ilegally in the first place..)

      Which leads me to believe their effort to sell lic. for Linux was only to show a market price for such so that they can rack up a high amount of "damage awards" against IBM, Et. Al.

      e.g., we would have sold 10 zillion of these your honor but the defentant released our IP so we need 50 zillion in damages; $50 for every copy of Linux in use...

      --
      http://www.hawknest.com/
    15. Re:Even if they offer a "download" by vk2 · · Score: 4, Informative

      If IBM added code to linux for which they didn't own the copyright - then its not GPL'ed even if the original author distrubutes the code that IBM added to to linux without proper copyrights. I agree they own the copyright to the stuff they wrote - hence the word "independent" in the memorandum.
      SCO is wrong as a matter of law, and IBM is entitled to partial summary judgment on SCO's contract claims, for at least two independent reasons.

      --
      No Sig for you.!
    16. Re:Even if they offer a "download" by mr_z_beeblebrox · · Score: 4, Funny

      I've been wondering why they haven't taken down the code from their servers. It just occurred to me that they may not have anyone in their company left who knows *how* to.

      Don't be a fool, EVERYONE at SCO knows how to take it down:
      TO:sco.com web server
      FROM: SCO Legal
      RE: Linux Download availability

      It has come to our attention that you are offering Linux source code for download. This is a direct infringement of SCOs valuable IP portfolio. SCO (caldera) has worked hard to get credit for other peoples work, you are diminishing it. You are hereby ordered to CEASE AND DESIST.

      Any lawyer can do that!

    17. Re:Even if they offer a "download" by CmdrGravy · · Score: 2, Insightful

      "To say that code included in SCO's Linux distribution becomes automatically GPLed is a red herring. If SCO was unaware of the presence of their code in the Linux kernel at the time, then the action was not voluntary."

      Assuming that it is a defence to say that you haven't checked the exact code you are releasing under a specific licence all that carefully and so didn't realise it was in fact derived from your own proprietary code then fair enough I agree with you.

      However now that they do know what the infringing code is ( as we know their MIT Deep Divers have identified millions of lines of code ) the fact they are still choosing to release it under the GPL means that they are know, knowingly, releasing that specific infringing code under the GPL which then undermines their case entirely.

      Your arguments about ditching the GPL in favour of a "free" licence are just nonsense. People who use the GPL do so because they don't want their work just hoovered up by anyone without them giving anything back to the original creator or the community at large - that's why they choose the GPL, because they like the protections it offers them.

      A lot of people/companies who would love to just use anybodies work they liked without the creator getting anything would love people not to use the GPL but that is never going to convince me the GPL is a "bad viral nastiness".

    18. Re:Even if they offer a "download" by m_evanchik · · Score: 2, Interesting

      That the left hand doesn't know what the right hand is doing at SCO should not come as a surprise.

      While the parent post was made in jest (or at least taken in jest), the reality may very well be that, on the technical side, SCO is so demoralized and moribund that they don't have anyone to monitor what is on their servers.

      My guess is also that the actual technical people at SCO are probably pretty disgusted with upper management's new strategy, and may be exhibiting some passive-aggressive behaviour by letting the GPL'd work stay online.

    19. Re:Even if they offer a "download" by msobkow · · Score: 3, Insightful

      Finally, it would seem rationality is coming to the forefront. Now lets see if the legal system has any sanity and quashes this SCO garbage already. We've all wasted far too much time and resources on the IP leeches already.

      At least maybe the mess will help force some changes on the USPTO. (No, I don't care how overworked you are. If you can't do the job right, then let the backlog build up until someone ponies up the resources to deal with the backlog.)

      --
      I do not fail; I succeed at finding out what does not work.
    20. Re:Even if they offer a "download" by phrostie · · Score: 2, Informative

      it means they have violated the copyrights of all the other kernel developers, because nothing else gives them the right to distribute it.

    21. Re:Even if they offer a "download" by Anonymous Coward · · Score: 2, Informative

      Well, they claim it is their code, it is downloadable from their website, as their product "SCO Linux", under the GPL. If that doesn't make the code in question released under the GPL, I don't know what does.

      It doesn't. Not much does, in fact. The only point that can be made is that, by offering the Linux code (the GPL'd stuff) along with their own code (their (alleged) kernel code, which we assume they don't wish to GPL), they are infringing on the copyright of the non-SCO code, by distributing it without a license!

      Really, the GPL can't force anyone to license their code in any way. The only thing it can do is to allow people to distribute GPL'd code, if they follow the rules. No rule-following, no distributy-allowy. Simple. And yet misunderstood so often, on both sides of the FOSS debates...

    22. Re:Even if they offer a "download" by Scarblac · · Score: 2, Informative

      Oh, I agree that they are in no way forced to distribute their code under the GPL.

      The thing is, they do distribute their code under the GPL.

      --
      I believe posters are recognized by their sig. So I made one.
    23. Re:Even if they offer a "download" by B'Trey · · Score: 4, Informative

      No, the GPL can't force them to do anything. That's the whole point. They were not forced. Grant that they are correct for a moment - that the Linux kernel includes code to which they hold the copyright. They certainly haven't proven this, but we'll give them the benefit of the doubt. Assuming this is true, they knew that the kernel in their distribution contained their own propreitary code. They knew that this code was distributed under the GPL. They did nothing to stop distributing the code. Of their own free will, without force from anyone, even after knowing that their proprietary code was in the kernel, they voluntarily made it available for download under the GPL.

      At a minimum, what makes code released under the GPL is when the owner of the code knowingly distributes that code under the GPL. SCO has done precisely that.

      --

      "The legitimate powers of government extend only to such acts as are injurious to others." Thomas Jefferson.

    24. Re:Even if they offer a "download" by Aim+Here · · Score: 3, Insightful

      Linus can't change the Linux license even if he wanted to. All of the 2-3000 contributors would have to agree to that or have their code written out. That is quite simply unrealistic and impossible.

      Hope this helps.

    25. Re:Even if they offer a "download" by slipstick · · Score: 2

      Actually I disagree. If I gave away your code that I didn't own under the GPL and you knew about it but continued to distribute the source under the GPL you would lose all rights to sue me. It doesn't matter that I didn't own the code.

      Your proper response would have been to sue me for copyright infringement, not distribute the code, and make it clear to everyone that is distributing the code, that you own the copyrights and haven't released it under the GPL.

      Now in IBM's case they do own the copyrights so it's even more clear, but in either case you can't stop me from doing something which you are knowingly doing even if I did it first. Of course you could claim you didn't know, but than how do you sue me? So once you know, you must stop distributing your own code under the GPL.

      --
      Sure information wants to be free, but how much are you willing to pay for the packaging?
    26. Re:Even if they offer a "download" by Curtman · · Score: 2, Informative

      Grant that they are correct for a moment - that the Linux kernel includes code to which they hold the copyright

      Don't grant that. They've been saying right from day one that this isn't about copyright. It can't be. They don't hold any copyright to the code in question, and Novell has cast doubt as to weather they own copyright to Unix even.

    27. Re:Even if they offer a "download" by ArtisteTerroriste · · Score: 2, Informative

      >The thing is, they do distribute their code under
      >the GPL.

      I believe they don't distribute any Sys V code under the GPL, because this is NO Sys V code in Linux.

      Anyone notice how IBM keeps saying in filing & court that to date, SCO hasn't provided a single line of infringeing code.

      Or as SCO says, referenced in this latest filing by IBM:

      "IBM keeps insisting on something that is not part of SCO's claims, so it should come as no surprise that files or lines of code in System V have not been identified"

  3. Patent hammer by nightsweat · · Score: 3, Funny
    I would think IBM would have a way to enforce its huge patent portfolio in a way that would torpedo SCO entirely, and not just in court.

    Maybe they could offer a $50/year licensing fee to other open source companies that use their patents and a fee of one BAZILLION dollars to SCO to use their patents.

    --

    the major advances in civilization are processes which all but wreck the societies in which they occur - A.N. White
  4. Scuppered? by YetAnotherName · · Score: 5, Informative

    Ah, "to scupper":

    v. 2. put in a dangerous, disadvantageous, or difficult position

    Yep, that's it.

  5. What's the quickest this could be finished? by Paul+Crowley · · Score: 5, Interesting

    If the judge basically doesn't extend SCO the benefit of the doubt any further on any of this, how long might it take for the whole thing to be completely dead, stop quivering, be visibly a corpse? How long can SCO continue to drag the threat out before it's dead?

    1. Re:What's the quickest this could be finished? by sotonboy · · Score: 2, Funny

      Sounds like a question for a slashpoll

    2. Re:What's the quickest this could be finished? by cdrudge · · Score: 4, Informative

      IBM files motion. SCO gets a chance to file a reply trying to debunk IBM's motion. IBM gets to reply to the reply. Then a hearing gets set. Then the judge rules on the motion.

      I think best case you are looking at a month or two, assuming nothing else gets done.

    3. Re:What's the quickest this could be finished? by prhodes · · Score: 5, Informative
      If the judge basically doesn't extend SCO the benefit of the doubt any further on any of this, how long might it take for the whole thing to be completely dead, stop quivering, be visibly a corpse? How long can SCO continue to drag the threat out before it's dead?

      It's going to be a while, I think:

      • 1. The whole business of the Partial Summary Judgement(PSJ) on IBM's 10th Counterclaim has to be resolved.
      • 2. This new PSJ has to be resolved (IBM filed, now SCO responds, then IBM responds to SCO, then there are oral arguments, then the judge issues a ruling)
      • 3. Any additional motions must be resolved.
      • 4. Whatever's left of SCOs claims goes to trial.
      • 5. IBMs counterclaims go to trial (this may be combined with 4, I'm not sure).

      So, it may be a while. I suspect IBM has other motions ready to gut the rest of SCOs claims, and these will need to be resolved. The only way I can see this resolved quickly is if SCO just folds, and that's IMO unlikely - it would expose them to massive shareholder lawsuits & probably an SEC inquiry.

      -Phil
      IANAL, I just read Groklaw

    4. Re:What's the quickest this could be finished? by slipstick · · Score: 5, Informative

      I agree its still going to be a while but I think we can make a better guess than that.

      The grandparent post stipulated that the judge wouldn't give SCO any more wiggle room, which I don't believe is all that far-fetched. Here, I take wiggle room as "we need more discovery", as opposed to "my nephews sick I need more time to file". The latter is what I would characterize as normal operations, the first is wiggling.

      IBM filed their first PSJ on or about May 21st. The initial oral argument was scheduled for Aug. 4th but this has been moved to Sept. 14th. Presuming a couple of days for the judge to ponder and that decision would be handed down around Sept.16th. So, let's call it 3 and 1/2 months. Thus, from the date of Friday's filing(Aug.13th) that would place a resolution on the contract question by or about Dec.1st or so, call it Dec.7th for good measure.

      Now, presuming further that both PSJ's go in IBM's favor, there would be little left to argue as the rest of SCO's case hinges entirely on their claims in the contract claims. I will guess that IBM will file a few more of these PSJ motions, basing them on the two already in play. So I will guess that by mid-May of next year almost all of SCO's case will have been dismembered. Effectively making "this" over. There will of course be the inevitable clean-up which will occur because IBM has all their counter-claims and I guarantee they are not going to let those drop. So sometime around November of next year I suspect SCO will declare bankruptcy or negotiate that IBM take over SCO operations with no money changing hands.

      Whether IBM desires to persue old Darl and his cronies for some malfeasance I can't guess in which case the "whole thing" won't be over for some time, but all the nasty stuff will be over by May or June of next year.

      IANAL yadda yadda yadda...

      --
      Sure information wants to be free, but how much are you willing to pay for the packaging?
  6. Re:I'd just like to say.. by SatanicPuppy · · Score: 2, Funny

    In other words you're glad they're getting slapped like the bitches they are?

    Word. Sue IBM? Bad idea. But if you do it, you best make sure you've got your shit together.

    --
    ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
  7. Summing up IBM's 100 page PDF in 1 sentence... by VC · · Score: 3, Funny

    Authored by: sef on Monday, August 16 2004 @ 11:34 AM EDT Posted on Groklaw, Sef is the author, not me.

    "We didn't do it. Even if we did, these guys said we could, but we didn't. And even if we did, which we didn't, not only did these guys say we could (but we didn't), but these nobks did the same thing, so we should be allowed to do it. Which we didn't."

    1. Re:Summing up IBM's 100 page PDF in 1 sentence... by Mr+Guy · · Score: 4, Funny

      One sentence? Must be some of that new math.

  8. Time for a class action suit by Tenebrious1 · · Score: 3, Funny

    Against SCO for making us with mod points have to dig through yet another SCO discussion.

    --
    -- If god wanted me to have a sig, he'd have given me a sense of humor.
    1. Re:Time for a class action suit by Armchair+Dissident · · Score: 3, Funny

      That's why I always mod in the morning before posting an article about SCO :-)

      --

      The ways of gods are mysteriously indistinguishable from chance.
  9. Costs ? by Anonymous Coward · · Score: 5, Funny

    I hope IBM follow this up with a request that SCO have to pay legal costs. 100 pages at rate even Tony Soprano would be ashamed at extorting ... erm charging ... should push SCO into chapter 11

  10. Derivative, but still important by grunt107 · · Score: 5, Informative

    IBM goes on to argue that old agreements with AT&T and expert witnesses make it clear that IBM was allowed to do what it liked with "derivative works." It would have been bad business for IBM to agree to broad terms banning it from controlling "derivative works," it says.

    If the AT&T contracts show the approval of derivative works, any AIX code IBM developed and then added to Linux would definitely be out of scope.

    I think someone is SCO-rewed on this one.

  11. Mwahaha by Anonymous Coward · · Score: 5, Interesting

    It's really cool to see how the things that we're pointing at here on Slashdot (like the still-available linux downloads) and going "wtf, SCO can't do that", we're finding eight months later IBM suddenly bringing this thing up in a legal finding and going "SCO did this, they can't do that".

    It's funny, IBM's legal team doesn't miss anything but they seem to always wait until the most opportune time to bring it up. Meanwhile even if SCO's case hadn't been baseless in the first place, they seem to be doing absolutely everything possible to sabotage it short of bribing the judge.

    Hey wait a minute, bribing the judge.. hmm...

    You know, something just occurred to me. I think I know what SCO might be up to. Have you ever seen "The Producers"?

    1. Re:Mwahaha by Mateito · · Score: 4, Funny
      Hey wait a minute, bribing the judge.. hmm...

      With what? Stock options?

    2. Re:Mwahaha by sharkey · · Score: 2, Funny

      Sure. Judges have to wipe their asses, too.

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
    3. Re:Mwahaha by Steeltoe · · Score: 2, Insightful

      Unless they go through every page on the SCO-site manually, they probably got it from some news-source. I wouldn't be surprised if searching through /. is actually becoming standard practice for lawyers to get ideas about their angle of attack/defence on technical issues.

      Don't underestimate the value of opinions from thousands of people across the globe.. It's unprecedented in our history. IBM certainly knows the open source community well enough to warrant that a substantial portion of their employees reads /. and similar sources.

  12. Puzzle Pirates Re:Scuppered? by kbs · · Score: 4, Funny

    It also happens to be the Puzzle Pirates filter replacement for the word fucked

    --
    yours,
    kbs
  13. scuppered ... again? by SABME · · Score: 5, Insightful
    With all due respect to Armchair Dissident, this is the first time I'm aware that IBM has refuted all of SCO's assertions on a point-by-point basis, and called into question SCO's motives in bringing this case to trial. So it's hardly the case that SCO is "scuppered again." It's just that the wheels of justice turn slowly, in the interest of giving all parties a fair hearing.

    According to Groklaw, this is nowhere near the end of the case, since SCO still has the opportunity to rebut IBM's motion, IBM then can refute the rebuttal, etc. etc. But it may be the beginning of the end.

    The previous "scuppered again" reports from Groklaw (and other sources) are the results of developments in other trials as well as independent investigations (outside the courtroom) into the merits of SCO's claims. Based on the linux community's technical consensus (again, outside of any trial) that SCO's claims are meritless, I think we've known SCO's case was doomed all along. We're still waiting for it to play out in the courts, though, which is where it counts.

    1. Re:scuppered ... again? by Armchair+Dissident · · Score: 4, Insightful

      I don't disagree with you at all. Indeed it is precisely because of SCO's constant ability to 'get out of jail free' that I made the remark. I don't for one instance believe that this is the end of the case, companies will always drag out a court case as long as they possibly can - and SCO has been particularly good in this respect.

      The "scuppered. Again" comment was mainly as a result of this from Groklaw:

      You don't want to miss reading page 76. It's where IBM tells the judge that as recently as August 4, 2004, SCO was *still* offering the Linux 2.4 kernel for download, the very code it is suing IBM over. [....] I think, therefore, that SCO's case just went poof, on this one issue alone.

      I think that Groklaw are probably right here. SCO no longer has the argument that they didn't know the code was still being distributed, so they have - by definition - been distributing disputed code under the GPL. Bang goes their case. But it's not the first time that their case has apparently gone Bang. All the claims of disputed code that turned out to be nonsense - for starters - should have scuppered their case. This one's going to drag on until SCO have no more money to fight with - IMHO.

      --

      The ways of gods are mysteriously indistinguishable from chance.
  14. Damn it! by tod_miller · · Score: 5, Funny

    I just gone and bought a license from SCO as well... and now you say they don't have a leg to stand on?

    www.ebay.com

    For sale, hardly used, SCO unix licenses.

    You beat their ass good big blue! I don't want thier own mothers to recognise them!

    SCO shows that everyone can hate you, and you can still try and make money. At least Microsoft stole thier crap from someone fair and square.

    --
    #hostfile 0.0.0.0 primidi.com 0.0.0.0 www.primidi.com 0.0.0.0 radio.weblogs.com
  15. So, which parts of the case is allready dead by KjetilK · · Score: 4, Interesting
    There has been a lot of stories on /. which says something like "if this goes through, the SCO case is effectively dead", and that "it is going to happen in weeks".

    I must admit that I have gotten a bit tired of SCO stories (weird, huh?), but I can't remember seeing a ruling that has killed parts of SCOs case.

    So, can somebody please summarize: Which parts of SCOs is dead now, by court rulings?

    --
    Employee of Inrupt, Project Release Manager and Community Manager for Solid
    1. Re:So, which parts of the case is allready dead by LowneWulf · · Score: 4, Informative

      Well the biggest part was the trade secrets claims. SCO rewrote their claims, dropping the pretense that SysV has any trade secrets, instead making the primary issue that of contract infringement.

      IBM has two motions for partial summary judgement in the queue. The first is for a declaration of copyright non-infringement. If this passes (to be evaluated in September), then the courts will declare Linux to be free from copyright issues from SCO. The second, this recent one, is for partial summary judgement against SCO's contract claims, which is what saves IBM.

      Linux wants the first. A lot. It effectively kills SCO's legal threat against Linux. The latter is what nails the most important part of SCO's case vs. IBM, and probably kills SCO in the process.

  16. Target acquired by Stephen+Samuel · · Score: 5, Funny
    SCO was still offering the disputed code for download as recently as August 4 2004.

    1. Target foot.
    2. Pull triger
    3. Scream
    4. Get bigger gun
    5. repeat 1-4
    6. Profit!!!! (M$)
    --
    Free Software: Like love, it grows best when given away.
    1. Re:Target acquired by David+McBride · · Score: 4, Funny

      You missed one:

      0. Insert foot in mouth?

  17. When will it end? by houghi · · Score: 3, Insightful

    I wonder how long it will take for SCO to trow in the towel. Not only that. I wonder what will happen AFTER they trow in the towel.

    My best guess is that they will drop all charges and as a result the other companies will drop their charges.

    The end result will be that our friend Darl has made a LOT of FUD and a lot of money. He has truly found the way to 3. Profit.

    --
    Don't fight for your country, if your country does not fight for you.
  18. Difference between IBM & SCO by CmdrGravy · · Score: 5, Interesting

    Reading the documents filed by IBM and by SCO I am constantly amused by the fact that I have no clue at all what SCO are getting at in there filings but the IBM filings are crystal clear and make perfect logical sense.

    The best bits of this filing I think are the pages and pages of testimony from ( by the looks ) almost everyone involved in drawing up the and signing the original contract who all say unanimously

    "This contract certainly does not provide SCO with the rights it says it is provided with, this was discussed at the time and all parties were agreed that it was not the case since to do otherwise would be so blatantly silly that no one would ever sign such a contract."

    Also the way IBM have culled SCO's many accusations to the single matter of the contract dispute and then ( in my opinion ) thoroughly destroyed that even more effectively than they destroyed SCO's previous claims is very impressive and kind of suggests that this has been IBM's plan all along and everything is moving very smoothly for them.

  19. SCO Stock is up! by chipwich · · Score: 4, Interesting

    SCOX (http://finance.yahoo.com/q?s=scox) is up almost 10% at of 10:30 EST. It must be true! Why does this stock move paradoxically to the news?

    1. Re:SCO Stock is up! by amacedo · · Score: 2, Interesting

      There is a good reason for this. Which is actually bad for SCO.

      Yesterday the stock hit the 52 week low has well as the same price it had *before* announcing it would fill the suit against IBM. Its just a bounce off a very value. Curiously enough there seems to be some volume.

    2. Re:SCO Stock is up! by div_2n · · Score: 4, Informative

      You may find some information on possible reasons here

    3. Re:SCO Stock is up! by Anonymous Coward · · Score: 5, Interesting

      The stock is *very* heavily shorted and thinly traded. Of the approximately 8.5 million shares that are available to be traded on the public market, more than 50% (that's 4 million plus shares!) are shorted. A typical stock is considered to be heavily shorted when it reaches 10-15%.

      This means that when someone wants to cover their short position, they push the price up somewhat.. particularly when it's heavily shorted and thinly traded. It's known as "short squeeze".

    4. Re:SCO Stock is up! by The+Analog+Kid · · Score: 2, Informative

      The stock is no longer being shorted as it's below $5, and it considered a "penny stock"

  20. Credit where credit is due. by throughthewire · · Score: 4, Insightful

    It's a bit disingenuous to say, "The Register is reporting..." and "Groklaw also has the story," when in fact Groklaw had the scoop on Monday.

  21. Re:There goes SCO's karma... by Andy_R · · Score: 4, Interesting

    the technical term for being -1 for lawsuits, is a 'vexatious litigant'.

    H.ere in Britian if you waste too much of the court's time, the court can declare you to be a vexatious litigant, and you lose the right to file suits. This would do wonders for SCO's share price!

    --
    A pizza of radius z and thickness a has a volume of pi z z a
  22. bring back..... by zogger · · Score: 2, Funny

    ....duelling.

  23. Groklaw has the story first, not "also" by Jayfar · · Score: 5, Informative

    Not to dis the Register, with their brief writeup dated today, but Groklaw had the story yesterday morning, including comprehensive analysis. To write that Groklaw "also has the story" is off the mark. Groklaw is, as usual, the preeminent primary source.

    1. Re:Groklaw has the story first, not "also" by Jayfar · · Score: 2, Informative

      True, good point. But for IANAL folks, such as myself, the Groklaw analysis is a big value add to the raw filings. Without that, many of the court documents may as well be written in sanskrit.

  24. SCOX Market cap 63.95M by Anonymous Coward · · Score: 3, Funny

    Q: Why doesn't IBM just buy out SCO for a cool 64M?

    A: They're probably getting more than 64M in free publicity from those jerks.

    1. Re:SCOX Market cap 63.95M by number6x · · Score: 4, Insightful

      How many other companies with small caps will line up to start suing IBM?

      If IBM earns the reputation as a company that will settle for a few million instead of fight, they will find themselves surrounded by mosquitoes!

      Look at Microsoft, they get sued all the time. MS is probably spending more on lawsuit settlements each year than they spend on keeping the XBox division or the Great Planes division afloat.

      IBM hasn't lasted over 100 years by giving money away to settle frivolous lawsuits. They know the long term consequences.

  25. Buy them by 5m477m4n · · Score: 2, Interesting

    With all the court fees, lawyers, and FUD that SCO is costing IBM, I would think it'd just be cheaper to buy them. There, now we most certainly own the code.

    --

    ---
    Those who can, do
    Those who can't, teach
    Those who don't know how, supervise
    1. Re:Buy them by 0123456 · · Score: 4, Insightful

      Buying them would merely encourage other dying companies to sue IBM. Better to beat them down into the dirt: even if it costs more in the short term, it will save money in the long term.

  26. Re:IBM by mr_z_beeblebrox · · Score: 3, Funny

    Sorry to say this, but IBM is going down...

    Yes they are! They are going down HARD on Sco. When they get up, they will brush SCO off their knees and do what they do.

  27. Re:There goes SCO's karma... by Anonymous Coward · · Score: 2, Insightful

    the technical term for being -1 for lawsuits, is a 'vexatious litigant'.

    H.ere in Britian if you waste too much of the court's time, the court can declare you to be a vexatious litigant, and you lose the right to file suits. This would do wonders for SCO's share price!


    Hmm, I don't know if we have such a thing in the States. Really I doubt it, a well applied ruling like that would help clear the civil courts of what we call "frivilious litigation". However, something like this could also be abused by using it to block unpopular causes or people who still have legitimate cases (i.e. civil rights lawyers in the 50's and 60's). So as long as you can trust your judiciary it could be useful.

    On a completely different note, does anyone else think that "Vexatious Litigant" should be a class in the mock-RPG ProgressQuest?:)

  28. No! by sethadam1 · · Score: 4, Insightful

    Why do people keep saying this?

    The company is already way overvalued! Why let all the execs and stockholders get lots of money for a company that has been nothing more than a dishonest bully?

    Anyone who is suggesting IBM buy them is completely missing the point. That's what they want!

  29. Re:Explain .... by Fnkmaster · · Score: 2, Interesting

    It's basically a gathering ground for trolls, where they post links to specific Slashdot posts that they want to be modded up (generally something that is trollish) in order to get lots of attention to it. Visiting the site itself won't hurt you, just don't click on the Slashdot links on the site unless you have HTTP referers disabled since apparently (according to the original post) Slashcode picks that up now and puts you on a moderator-banned list.

  30. How did the Registry get it so wrong? by slipstick · · Score: 5, Interesting

    The Register claims "IBM goes on to argue ... that IBM was allowed to do what it liked with derivative works."

    This is NOT what IBM's motion claims. In fact it's the exact opposite of what IBM was arguing. IBM's motion claims that the agreements with AT&T applied only to "derivative works" as defined by the US copyright office and truck loads of case law. "Derivative works" here having it's naturally understood meaning that the work must contain part of the original(or some substantial simularity).

    So basically IBM was saying that they aren't allowed to distribute the source code to ALL of AIX or Dynix or any part that CONTAINS System V code, but they can distribute any of the code from these that belongs only to IBM(called homegrown code in the motion).

    Since noone is claiming that IBM has given away all the code to AIX and Dynix, and because SCO has basically given up any pretense of showing code in Linux that might have come from System V AND because the only code SCO has actually pointed to belongs ENTIRELY to IBM which is expressly NOT derivative code, than IBM is well within their rights to distribute it.

    In other words, "It belongs to us and we can do with it what we like, now piss off."

    As opposed to "Sure part of it belongs to you but the contract says we can do with it what we like, so piss off". If this was the case I would be backing SCO here, but since it isn't, I want SCO to fry.

    --
    Sure information wants to be free, but how much are you willing to pay for the packaging?
  31. I've made them an offer... by Saeed+al-Sahaf · · Score: 2, Funny
    The company is already way overvalued!

    I sent an offer of $699, but as yet I have no response. I think it's quite generous, I can't imagine what's keeping them.

    --
    "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
  32. missing the point by einhverfr · · Score: 3, Informative

    You folks are talking copyright here, and IBM's hearing on Partial Summary Judgement on this issue is next month (they filed this motion some time ago).

    This story is about IBM moving for PSJ on the contract claims, basically stating (among other things) that the court should be able to rule on whether IBM is permitted contribute their in-house code into Linux as per the AT&T contract. This is actually quite a bit worse for SCO than just a copyright PSJ because this will hurt many other aspects of their case.

    IANAL, etc.

    --

    LedgerSMB: Open source Accounting/ERP
  33. Not quite right... by mark-t · · Score: 4, Informative
    FTA on Groklaw...
    In the beginning of the case, they said they didn't know the allegedly infringing code was in there when they released Linux under the GPL. They can't say that since they filed the lawsuit in March of 2003. Now, in August of 2004, they are *still* distributing the same code under the GPL. Under the terms of the GPL, there is no taking that code back that I know of. I think, therefore, that SCO's case just went poof, on this one issue alone.

    Remember, since SCO was also alleging that the terms of the GPL itself were not valid, the fact that they continued to distribute it under the terms of the GPL was meaingless.

    What this does *NOT* do, and they are right to assume this, is automatically make the GPL apply to their code, since there was no obvious intent to do so. If the GPL is not valid then absolutely nobody, including SCO, has permission to distribute Linux without permission from the copyright holders on the code. Does SCO have this permission outside of the terms of GPL? No? Then it makes SCO guilty of continued and willfull copyright infringement.

    1. Re:Not quite right... by gvc · · Score: 4, Insightful

      IBM has a separate counterclaim re GPL and violation of IBM's copyrights.

      Their point in this request for summary judgement has nothing to do with GPL. All they are saying is that SCO can't expect IBM to keep it (JFS etc.) confidential while they (SCO) continue to publish it. As SCO has stated over and over, this particular claim has nothing to do with copyright, and therefore nothing to do with GPL. It has to do with confidentiality.

  34. another egregious error by The Register by ToLu+the+Happy+Furby · · Score: 3, Informative
    The Register wrote:
    "Second, even if the AT&T agreements could be read to preclude the disclosure of homegrown code - and they cannot be - any breach based upon such a reading has been waived by Novell on behalf of SCO, and by SCO itself," IBM says in the filing, referring to the time in which Novell owned the rights to Unix before SCO.

    Totally wrong. Instead, IBM is referring to the fact that Novell only sold some Unix rights to Old SCO, and that among the rights they retained was the right to direct SCO to "amend, supplement, modify or waive any rights under, or assign any rights to, any System V License". And, in the event that SCO refused, to do so themselves.

    More broadly, SCO did not buy the existing System V licensing business from Novell. They only bought the right to sell new Unix licenses, and also to handle administrative duties on existing licenses in exchange for a 5% commission. IBM's Unix license is still with Novell, not SCO. SCO acts as a go-between on Novell's behalf, but that's the extent of their role.
  35. This is the SECOND summary judgement motion by Animats · · Score: 4, Interesting
    This new motion is IBM's second motion for partial summary judgement. The first one, asking for dismissal of the copyright claims, was supposed to be decided this month, but that's been put off until September 15th. If the copyright claims are dismissed, it's over for everybody but IBM. That's the one we all care about.

    The new motion is about IBM/SCO contract issues. That doesn't directly affect anybody else. Only the copyright claims matter to unaffiliated third parties.

  36. New theory - IBM did it by TimButterfield · · Score: 2, Interesting

    or some other pro-Linux company.

    Wait. Wait. Here me out. I am just playing the devil's advocate here to bounce an alternative theory off of the group. I do not think this is true, but 'what if' ...

    This is the scenario:

    1. A (privately) known bad case is put forth with great publicity.
    2. Distrust regarding Linux is created due to the FUD surrounding the case.
    3. After a sufficient length of time, the case is publicly shown to be legally invalid.
    4. The case collapses.
    5. The negative becomes a positive.
    6. Profit!

    I know, too many steps.

    It is easy for many /.ers to think of Microsoft as the evil giant seeking to destroy Linux. What if this case is more like a legal vaccination? The SCO case could be used to create legal precendents to make it more difficult to attack Linux in the future. That which does not kill you makes you stronger.

    To repeat, I do not think this is what is happening, but I do find it interesting to consider the possibility.

  37. Because... by schon · · Score: 4, Interesting

    Why can't SCO Claim.

    1) we didn't know it was there


    Because they're still distributing it themselves.

    2) Once we found out it was released everywhere by IBM the horse was way out of the barn.

    Irrelevant. If you want to try to claim damages, you MUST do everything in your power to stop infringement.

    3) IBM'S "illegal" actions have boosted the Linux market place

    Again, irrelevant. How popular something is has no bearing.

    4) To stay competitive we have to release a copy of Linux, under GPL, to be competitive.

    That does not logically follow. Damages have no bearing on you continuing to be competitive or not.

    5) But all of this is a result of the fruit of IBM's "illegal" actions so they still owe us damages.

    By continuing to distribute it themselves, they are declaring that the value of the infringement is $0.00. There are no damages to be awarded.

    Here's what SCOX should have done:

    Once they discovered the 'infringing' code, they must immediately stopped distributing the material themselves, then contacted the responsible people to arrange for damages (which they claim was IBM.) In doing so, they must (as a matter of law) identify the lines of code that are 'infringing'.

    They should then contact every distributor of Linux they know about (I'm guessing that a notification sent to Linux, kernel.org, along with a press release might be acceptable in this case), and notify them of the status of their claim, the lines of code that were at issue, and demand that they cease distributing the 'infringing' material.

    Failure to follow these steps means that they can't claim damages.

    There is *NO* (as in zero, nil, nada, zip, bupkiss) valid legal reason to not follow these steps, and many valid legal reasons they should.

    The only answer as to *why* they didn't is as follows:

    Either 1) they know they have no case, or
    2) their lawyers don't know anything about the law at all, and should be disbarred and charged with fraud.

  38. Distributing should NOT be heald against SCO by Ungrounded+Lightning · · Score: 3, Insightful

    In my opinion, a company's distribution of source for GPLed products for which it released versions should NOT be held to void its IP claims to any of its proprietary code inserted by others - even if it continues to distribute versions containing the code. I see this as both a matter of law, derived from the GPL's own terms, and as a matter of good policy for GPL promotion.

    The GPL explicitly claims that it does NOT purport to grant a license to proprietary code improperly inserted into a GPLed distribution by someone who does not have the necessary rights to place the code under GPL. But it does demand that any person (or company) who distributes object containing GPLed code must make the source available, and if even one copy goes out without the source attached the only permissible way to do that (so it can reach a repurchaser of the oject) is to make the source available generally for a minimum time, as by a web or FTP site.

    So a company who distributes a modification of a GPLed project may be required to distribute the code for a time, under penalty of loss of the right to copy and/or distribute GPLed code forever. If the company THEN discovers someone ELSE has included their pride-and-joy in the base distribution, they're in a catch-22:

    - If they stop distributing the source, they lose GPL rights. This could be a BIG cost.
    - If they DON'T stop, AND this puts their proprietary code under GPL, they suffer the loss of their IP.

    So the doctrine of estopple should not apply: Their IP is already exposed - taking down their distribution won't significantly mitigate that damage, since it will be available elsewhere on the net. But taking it down WILL generate other costs for them.

    And since the GPL doesn't claim to grant rights to code improperly inserted, it can be argued that the improperly inserted proprietary code is not under it, until such time as the owners deliberately, with intent, insert it themselves - despite their continued distribution of the source improperly containing it, in order to meet their GPL obligations.

    Now the GPL advocates might want to argue that, nevertheless, the victim of such theft must now either free the code or stop distributing and lose all GPL rights. But IMHO that's a bad idea.

    Such a position would greatly hamper the adoption of the GPL codebase by companies with code they wish to keep proprietary - because unknowing propagation of code stolen from them within a large software release (such as a Linux distribution) would leave them on the above cleft stick: Give away your family jewels, or suddenly shut down all your GPL business-model activity.

    Of course IBM's lawyers had to try making this assertion. But for the future of the GPL I hope that either the case is decided without a ruling on this issue or (better yet) IBM's claim that this frees the (allegedly) SCO code is explicitly rejected.

    (Meanwhile, perhaps the maintainers of the GPL might want to add a bit of verbage to clarify this issue to a future version?)

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    1. Re:Distributing should NOT be heald against SCO by fymidos · · Score: 2, Informative

      >In my opinion, a company's distribution of source
      >for GPLed products for which it released versions
      >should NOT be held to void its IP claims

      If a company puts code under GPL, it does not lose IP rights. They can still sue anyone who does not respect the GPL (under which the code is licensed).

      If they stop distributing the code they do not lose any "gpl rights". And they can always distribute "their" code in any license they see fit. However, most the code in question is really IBM's code, so such a move would propably ignite a furious counter-attack.

      >Their IP is already exposed

      It is not their IP. The court will have to decide that, since it still is IBM's IP unless proven differently. However *if* they really felt it is their ip they should/would distribute the code under the license they see fit. This is a weak point in their argument. See, if that is the case, and it is their IP why did they choose GPL to distribute it?

      >the maintainers of the GPL might want to add a
      >bit of verbage to clarify this issue

      There is no issue here: if stolen IP is inserted in GPL code, GPL is very clear about it. Only this is not stolen IP and the whole case is not about that.

      If what you describe ever happens, the company in question will simply distribute their code with their choice of license and GPL code with GPL license.

      --
      Washington bullets will simply be known as the "Bulle
    2. Re:Distributing should NOT be heald against SCO by Ungrounded+Lightning · · Score: 2, Interesting

      Wow, you've bought into SCO's position regarding their distribution of GPL'd code.... that it was improperly added by a third party and their subsequent distribution does not obligate them to honor the GPL's terms because they were deceived.

      Not at all.

      I'm saying that:

      - The GPL itself CLAIMS not to apply to code illegitimately inserted.

      - That leaving no way for companies that are in the position SCO claims to be in to defend IP they did not intend to release will result in companies that otherwise would release SOME of their code under GPL chosing to release NONE, for fear of compromsing the REST of it.

      This would greatly reduce the amount of code released under GPL. So the issue needs to be addressed - if nothing else, to eliminate the ambiguity.

      1: Regarding "greatly hamper the adoption", you're just dead wrong. Take a look around. Adoption of GPL code is progressing very well. Linux is growing dramatically.

      Yes it's progressing. But I claim it will progress faster if the issue is addressed than otherwise.

      Meanwhile, let's see how the results of the SCO suit affect the progress - especially if the "meeting GPL obligations legitimizes past 'theft'" doctrine is accepted by the courts.

      2: The primary purpose of the GPL is to ensure freedom to modify and distribute original and modified code. That is why the GPL exists, not to enhance adoption by companies with particular proprietary interests.

      It is also there to encourage the release of code to that commons. By guaranteeing your not locked out of future revsions of your own code it encourages that release. But if it puts at risk code you didn't intend to release, it discourages release.

      I claim we can have both those cakes, not just one.

      --
      Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  39. Waiting for boat at train station by salesgeek · · Score: 2, Insightful

    What's really interesting about all this SCO nonsense is that thier case seems to share a philosophy I see often on /. concerning intellectual property:

    1) An overbroad definition of derivative works and an understanding that I build part A. You build parts B, C, and D on part A. All your parts are belong to us, thank you for playing.

    2) Somehow that I worked on your code in the pase prevents me from creating new simmilar code in the future. If you do create it, I own it.

    All of these ideas are flawed in that they assume that intellectual property is like a rental property where all your improvements belong to the landlord.

    --
    -- $G
  40. IBM wins for creativity in punishing SCO... by gsfprez · · Score: 2, Interesting

    Notice who they got to compare Linux and SVRX (and AIX and Sequent) code against each other?

    A REAL LIFE MIT scientist... and not just any fictitious MIT scientist.... but Dr. Randall Davis, Director of Research for CSAIL.

    i read that and said to myself... wholly fscking shit... THAT is funny.

    --
    guns kill people like spoons make Rosie O'Donnell fat.
  41. Interesting point by MarkusQ · · Score: 4, Insightful

    While I agree with you in spirit, I can't help but think that what you are suggesting would be far worse than the problem it proports to solve. If someone knowingly distributes something they wrote under the GPL, then they have done just that. No waiting for an indefinite period and saying "April fools!" or "Gosh, we knew our code was in the stuff we were distributing under the GPL, but we didn't intend it" or shouting "Psyche!" at the world.

    In the circumstance you discribe, there must have been some other version of the software, distributed under some other terms, before it was ever added to the GPL'd aglomeration. What they should do is strip their code out, and distribute the GPL'd mass minus their code under the GPL, and offer their original product under whatever licence they wish.

    They don't have to "stop all their GPL activities" but they shouldn't knowingly distribute something under the GPL (or, for that matter, under any licence) if they don't intend to honour its terms.

    -- MarkusQ

    1. Re:Interesting point by Curtman · · Score: 2, Informative

      And of course we need to come back to the central issue. The code in question is NOT sco's. They don't own the copyrights for JFS, NUMA, RCU, etc. They only claim (in the most confusing possible way) to have authority over IBM via its licensing so they can dictate what IBM can and can't do with its OWN code, they they wrote, and have copyright of. Anything else that comes out of McBride's mouth just sounds like that gurgling sound that toilets make when you flush. I subscribe to the JFS mailing list, and have for quite some time. Even a casual reader would pick up on the fact that the JFS in Linux is not from the same lineage as the JFS in AIX.

    2. Re:Interesting point by MarkusQ · · Score: 2, Insightful

      If they (our hypothetical potentially wronged propritary software developer) want people to to take their claims seriously, they should conduct themselves in a manner that supports that position. In other words, do what's right rather than what's expedient. This is generally known as "acting in good faith".

      Suppose they are distributing a binary mass of GPL'd goo, call it BGv13, and the associated source code SCv13. One day they discover that it contains proprietary code P. What should they do?

      1. Stop distributing BGv13
      2. Notify the world that they should also stop, and explain clearly what the problem is. Note that under the GPL, the world would be obligated to listen.
      3. Notify everyone to whom they gave BGv13 that there is a problem and a update will be coming soon.
      4. Produce SCv14 = SCv13 - P, and compile it to produce BGv14. Start distributing that.
      5. Notify the people from whom they got the tainted version of the problem, and work with them to resolve the problem.
      6. If anyone to whom they had given BGv13 asks for the source, they should appologize and explain that the source for that version is unavailable due to licensing problems, and send them BGv14 & SCv14
      All of this should be done as soon as possible, and in a non-confrontational manner. Once they are not themselves contributing to the problem, they may want to pursue the matter (at apropriate levels of firmness) with anyone who is still distributing P without a license.

      What they should not do is continue providing BGv13 for over a year, threaten people right and left, but refuse to tell anyone what P is or why they even think it's in SCv13 in the first place.

      It isn't rocket science. What do you do if you find out that you're in the wrong seat at a concert (or someone else is in your seat)? What do you do if someone starts reading your paper on the subway? Do you atempt to resolve things reasonably, communicating what you think the problem is, or do you start by yelling, threatening, etc.?

      -- MarkusQ

  42. Re:Patents by HiThere · · Score: 2, Interesting

    The GPL prohibits this for code that IBM distributes. But IBM doesn't distribute much GPL code (except internally). That is why it is important that:
    a) the cost be nominal (it's a non-recoverable sunk cost), and
    b) the license be irrevokable, and entend to those who use n-th generation copies/derivations.

    OTOH, to the extent that IBM has distributed GPL code to those customers who run Linux on IBM mainframes, IBM has already waived those rights. (I don't know how significant this is.)

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  43. IBM is fighting this the only way it can by phrostie · · Score: 2, Funny

    IBM is fighting this the only way it can be faught.
    SCOX has been playing a shell game of issues and evidence.
    when ever IBM has asked to define the issues or evidence SCOX has moved to the
    next wallnutshell.
    what IBM has done is to say to the Court, OK, but they can't go back to that
    later. one PSJ is bad enough for SCOX, but when they start adding up SCOX
    starts to run out of wallnuts to use for misdirection. before long they will be
    sitting at a table with all their nuts smashed.

  44. A text-book case. by biendamon · · Score: 5, Insightful

    That logical critique of Enderle's keynote belongs in a text-book. It is systematic and devastating. Nothing I can say will do it justice, so I'll just recommend that Slashdot readers interested in logical argument construction (and deconstruction) read the piece. It's long, but well worth it.

  45. My summary of the memorandum by UnknowingFool · · Score: 2, Insightful
    IANAL but here's my summary of the memorandum.

    First, SCO says that IBM stole millions of lines of code and put into Linux. IBM has asked SCO to identify the lines many times. A judge has ordered SCO to do so twice. SCO has not done so to this date.

    Instead, they keep changing their claim. Then the case became about "trade secrets" IBM stole. IBM has asked SCO to identify what trade secrets or what code are invovled with these trade secrets.

    SCO no longer says its about trade secrets. Now, it's about code that IBM contributed from AIX and Dynix into Linux. SCO argument is that since they own System V, according to the licensing agreements between AT&T and IBM, they own all dervatives and anything else IBM creates. Thus IBM cannot contribute code to Linux because SCO owns it. SCO does not identify all the lines but does identify the modules that contains this derivative code (RCU, SMP, etc). Because IBM violated this agreement, SCO has the right to terminate IBM's license.

    Using an expert from MIT, IBM says that all the modules that SCO mentions contains no derivative code but is original.

    IBM mentions Amendment X. Back in 1996, in an agreement (Amendment X) with Novell and old SCO, IBM acquired a "irrevocable, fully paid-up, perpertual" license to System V for the sum of $10 million. Novell eventually sold some rights to SCO but kept enforcement rights.

    IBM then brings out everyone and their dog that participated on the original license from AT&T, IBM, and Sequent. Everyone involved agree that AT&T does not and never owned any derivatives of System V created by their licensees or by third parties for their licensees. All parties (especially AT&T) emphasize that any original code created by their licensees and not derivative were never claimed by AT&T. Since AT&T never claimed it, SCO cannot either. AT&T reps and former counsel disagree with SCO current interpretation of the license agreement that AT&T drafted. IBM supports this with a few documents from AT&T including the $echo newsletter.

    So as a matter of law, IBM says that summary judgment should be granted because it is all one-sided. Citing case law since everybody who was party to the original license agrees with IBM and all documents support their view and SCO has not produced any testimony or documents otherwise, IBM owns all their own original code and any derivatives of System V. Thus they could not have breached the contract.

    Also, even if IBM breached the contract, the contract cannot be terminated because of Amendment X. Additionally, even if the contract could be terminated, SCO does not have the right to do so. Novell still retains the enforcement rights of System V. Lastly IBM notes that SCO should not be able to sue IBM over contributions to Linux if SCO itself still distributes Linux knowing it supposedly has "stolen SCO code"

    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  46. Is it just me by nickthisname · · Score: 2, Funny

    or does anyone else think SCO should go back to their orignal name of Caldera, since that is Greek for "big hole in the ground" ?