Slashdot Mirror


SCO Terminates IBM's Unix License

AKAImBatman writes "SCO has terminated IBM's license to use Unix code. SCO is filing for an injunction that will require IBM to cease all sale of AIX as well as accrue damages for each day IBM continues to sell AIX."

23 of 1,065 comments (clear)

  1. Insanity! by jmorris42 · · Score: 5, Interesting

    I can't believe they are this stupid! How can they possibly claim that
    IBM customers are operating without a valid license? SCO does not
    dispute that IBM possessed a valid license up through the end of Fri 13.
    So any copies that IBM sold before that date are perfectly legal licenses.

    Any court that even takes any other legal theory seriously will destroy
    the entire US economy by creating uncertainty in ALL sub-licensed IP.
    And I have just enough faith remaining in the US legal system to believe
    that the judge will be bright enough to see the can of legal Whoop-Ass SCO is asking them to open.

    --
    Democrat delenda est
    1. Re:Insanity! by firewood · · Score: 5, Interesting
      No, imagine for a second what would happen if they actually were to get their injunction requiring each and every copy of AIX to be collected and destroyed. The National Weather Service is using AIX...

      That's an easy one. Congress can just use eminant domain, and nationalize all rights to *nix as a public right-of-way. Same as what they do for any roadways deemed necessary for the public safety, national infrastructure, etc.

    2. Re:Insanity! by Surak · · Score: 4, Interesting

      The National Weather Service is using AIX for some of their weather modeling. What do they do, just cease operations for a few months while they port their software..... to WHAT? None of the other commercial UNIXen are safe, you can bet they aren't stupid enough to try porting to a rack of Dells running NT.

      Personally, I'd go with either OpenBSD or Linux. OpenBSD is proven to have rock solid stability, and recent Linux kernels are pretty good. And Solaris has good stability on the right hardware -- say, an Enterprise 10k.

      If you write for 1 *nix, porting to other *nixes isn't that hard as long as you write your code in something portable, like ANSI C.

  2. So, this could be a blessing in disguise by aelfwyne · · Score: 4, Interesting

    If SCO is seeking an injunction, does that mean they would have to prove to a judge that there is sufficient evidence for such an injunction? And if they do happen to convince a judge...

    Well, better that IBM be the one to take on SCO rather than a group of Linux volunteers or users.

    I just hope IBM doesn't cave. They've shown incredible lack of backbone in the past when push came to shove (OS/2 backing out of desktop market anyone?), let's just hope this isn't one of those times.

    --
    -- If it ain't broke - overclock it more.
    1. Re:So, this could be a blessing in disguise by DutchSter · · Score: 4, Interesting

      If SCO is seeking an injunction, does that mean they would have to prove to a judge that there is sufficient evidence for such an injunction? And if they do happen to convince a judge...

      What's interesting is that they are seeking a permanent injunction. Such an animal is generally part of the "punishment" phase. Seeking a permanent injunction now is part of the legal process to say that IF I WIN THE CASE, I want them to stop forever. I think it's interesting that they have not gone for the TEMPORARY injunction that they said they would. A TRO is typically issued before the whole case gets underway and expires at some phase of the trial.

      In order to be granted a TRO, you must show that not only will you be harmed if the action continues, but that the harm will be direct and irreparable and that you have a reasonably high probability of proving your case. Without being able to prove irreparable harm, judges generally like to maintain the status quo until the whole thing is sorted out.

      From my experience in the legal field, if they grant their opponent 100 days to "Fix it up", they would have a higher burden of proof to say that they are being irreparably harmed as each day goes by than if they filed suit right away. A judge is more likely to look at this case and say "Well, you might be harmed somewhat, assuming your allegations are true, but you put up well enough for three months, another two months to sort this out probably won't be irreparable. Motion denied"

      Consider another use of TROs: battered women are generally granted TROs after a domestic dustup the night of, or the following morning. Such matters are so urgent that they cannot be delayed even a day. Giving someone 100 days to clean up just seems to show that you can tolerate it better than you would otherwise admit.

  3. SCO is hard to believe here by chrysrobyn · · Score: 5, Interesting
    SCO notified IBM on March 6, 2003 that it intended to terminate in 100 days, as required under the Software Agreement, as modified by a side letter, if IBM did not correct certain actions that violate the agreement. As of the deadline -- 12:00 midnight, June 13, 2003 -- IBM had not complied with SCO's request, which triggered the termination. The termination is self-effectuating.

    In order for IBM to be able to comply with certain actions, as I understand it, IBM would have to either:

    A) Stop selling AIX.

    B) Remove the offending code from Linux.

    In order to do A), well, IBM would have to give up. In order to do B), IBM would have to have a copy of what SCO thinks is the offending code, review it, engineer suitable replacements, and submit patches to Linus. I don't think Linus would necessarily have to accept it for IBM to prove that it has done all it could. But, I believe we've read before, SCO didn't want to share its violated code until last week or so. If IBM didn't have access to that until last week, SCO was asking IBM to take their word for it. Doesn't sound very legal to me.

    I've seen IBM work. Sometimes it's slow, but sometimes they can move a staff of 300k people so quickly the earth spins the other way. I've got to think that IBM has enough talent to replace many 60 line blocks and have them tested before 100 days had expired, if given a fair chance.

    Last night, I had convinced myself that I thought it was reasonable for IBM to be dual licensing code they had written. I'm still not sure SCO has proven IBM has liberated code, but if it had, and it was originally IBM's, why not allow it?

    By stating "IBM has clearly demonstrated its misuse of UNIX source code..." by "using UNIX methods to accelerate and improve Linux as a free operating system", is SCO saying that even if a completely disparate group of Unix virgin IBMers couldn't work on Linux without undermining the contract? That sounds awefully strict.

  4. Pissing in the Well by rossjudson · · Score: 5, Interesting

    The real issue that's going to be litigated here is to what extent SCO can claim damages from another company if the infringement is tiny. The very best thing that SCO can muster, in this case, is that they've identified a subroutine or two that seem to be close or identifical to something they claim is their own code. Let's suppose that this is true. What effect does this small infringment have on the entirety of Linux? Can they claim that Linux is an infringing product when only a tiny part of it contains (arguably) any SCO code?

    The court is going to have to struggle with this part/whole issue. If I had to guess, I'd say that if it hit a jury, the jury would tend to be fairly absolute -- as in, you copied this tiny bit, so now you're liable for the whole thing. A judge is probably going to weight the infraction versus the whole.

    And I really don't know what the law is on this. Maybe a legal type can help us out here.

    1. Re:Pissing in the Well by MeanMF · · Score: 4, Interesting

      The real issue that's going to be litigated here is to what extent SCO can claim damages from another company if the infringement is tiny. The very best thing that SCO can muster, in this case, is that they've identified a subroutine or two that seem to be close or identifical to something they claim is their own code.

      They're claming much more than that now - in a recent interview their CEO is now claiming the following:
      "We're not talking about just lines of code; we're talking about entire programs. We're talking about hundred of thousands of lines of code...We're talking about line-by-line code copying. That includes not just the function but the exact, word-for-word lines of code. And the developer comments are exactly, 100 percent the same."

  5. In related news... by phathead296 · · Score: 5, Interesting

    IBM's stock is up over 2% today while SCO's stock (SCOX) is down over 2%.

    Nice to see Wall Street react appropriately to this news.

  6. Take a hint from greenpeace? by earthforce_1 · · Score: 4, Interesting


    I heard a common environmentalist tactic was to have a large number of individuals buy exactly one share of a corporation they disliked, then show up en mass at the shareholders meeting, (they cannot be refused entry as a shareholder) and liven up the party.

    --
    My rights don't need management.
  7. AT&T may be getting in volved as well. by eric76 · · Score: 5, Interesting

    From http://www.infoworld.com/article/03/06/16/24OPcrin gely_1.html:

    Without even knowing it, SCO may have started a war of attrition with much larger enemies that have deeper pockets. Within the halls at AT&T, folks were chattering just last week that AT&T still has reserved rights on Unix. Naturally, the company is paying close attention to the various legal claims that SCO is making and may join the battle soon. My spy said the word around AT&T is that this will all be resolved shortly. But one has to wonder how long SCO could survive if it had opponents in multiple courtrooms â" those being, of course, IBM and AT&T.

    I wonder what rights AT&T retained.

  8. Re:Another URL by walt-sjc · · Score: 5, Interesting

    ... And in this news.com.com.com... story, there is a quote from SCO claiming "This termination not only applies to new business by IBM, but also existing copies of AIX that are installed at all customer sites. All of it has to be destroyed."
    That is something I have not heard SCO claim before. I was under the impression that they wanted to cut off future sales, but all past sales too? The insanity never ends at SCO.

  9. Re:don't miss the McBride interview... by Ami+Ganguli · · Score: 4, Interesting

    They're using an extremely broad definition of "derived". From that interview it's finally clear what they're trying to claim.

    They're saying that they have rights to any technology that any Unix company ever added to Unix. So the JFS, for example, which was added by IBM to their Unix derivative, can't be added by IBM to any other software (including OS/2 I suppose, which is where the Linux version actually came from).

    I really doubt that IBM was stupid enough to sign something that broad. In fact, it would be far more viral than the GPL. If I incorporate my proprietary code into GPLd software, I can still retain copyright to the code and continue to use it in my own projects. Apparently not so with SysV code.

    --
    It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail. - Abraham Maslow
  10. Interesting interview notes by joncarwash · · Score: 5, Interesting

    In the various interviews and statements that have come out of SCO over the past few months, there has definitely been some conflicting information. In this most recent interview, I find a number of things peculiar, but this is what jumps out at me first:

    When we take a top-tier view of the amount of code showing up inside of Linux today that is either directly related to our Unix System 5 that we directly own or is related to one of our flavors of Unix that we have derivative works rights over--we don't necessarily own those flavors, but we have control rights over how that information gets disseminated--the amount is substantial. We're not talking about just lines of code; we're talking about entire programs. We're talking about hundred of thousands of lines of code.

    Note how he says "entire programs"; the basis of the complaint is that code was copied into the Linux kernel. Apparently they are also claiming that some GNU tools and other programs are also "copied." From what I understand of the initial press releases, SCO was suing over certain multi-processor related functions of the kernel which apparently came out of Project Monterey, which IBM and SCO were a part of.

    He does state in the interview that this is a lawsuit for breach of contract with IBM, and not copyright or patent infringement.

    And when we filed against IBM, we chose to not even talk about copyrights.

    So, it is interesting that he is proposing taking Linux distributors (Red Hat, SuSE, etc.) and possibly other Linux users to court as well. If they are not on solid ground suing IBM over copyright infringement, how are they going to manage to sue all of the linux distributors and users on the planet for copyright infringement - since these distributors and users never had any contract with SCO.

    For a final major thought, all of this "copied code" is appearing in both Sys V and Linux.. where does BSD come into play? Could the code from both places have been taken from BSD? Of course with the terms of the NDA that SCO makes you sign, I am sure that you couldn't compare the Sys V code to BSD, only Linux.

    PS: Why hasn't someone run the Sys V and Linux code through a copied code detector program (like some college professors use to stop code copying on assignments). Obviously this would be a much larger scale project, but if SCO's UnixWare has such great multi-processor capabilities, they should be able to figure something out. And if there is so much copied code, it should be no problem to find it using this program. Show us the stats, at least.

    --
    A computer is a valuable tool, so use it and stop whining.
    1. Re:Interesting interview notes by Platinum+Dragon · · Score: 4, Interesting

      We're not talking about just lines of code; we're talking about entire programs. We're talking about hundred of thousands of lines of code.

      Note how he says "entire programs"; the basis of the complaint is that code was copied into the Linux kernel. Apparently they are also claiming that some GNU tools and other programs are also "copied."


      [...]

      So, it is interesting that he is proposing taking Linux distributors (Red Hat, SuSE, etc.) and possibly other Linux users to court as well.

      Or, at least, taking a good shot at slagging Linux coders and users as anti-IP thieves, a tactic that MS tries using from time to time. This, obviously, can do great harm to the reputations of Linux companies, and thus reduce their revenues, possibly to the point of bankruptcy.

      If McBride's numerous allegations prove unfounded, so much vapourware, there is a word Slashdotters should become familiar with, as it will likely be the focus of many lawsuits against SCO and McBride, or just McBride if SCO is obliterated by IBM.

      Slander.

      --

      Someday, you're going to die. Get over it.
  11. Re: Clarification? by Cid+Highwind · · Score: 4, Interesting

    To sum up:
    1: SCO bought the copyright to UNIX from AT&T
    2: IBM licensed UNIX code from SCO
    3: IBM put UNIX code into AIX (that's what they licensed it for)
    4: IBM made lots of money selling AIX systems to big companies
    5: IBM had another team forking on Linux
    6: SCO claims that IBM put UNIX code into Linux (violating the terms of their license)
    7: SCO canceled IBM's UNIX license because of the alleged violation of their contract
    8: SCO released scary-sounding press releases implying that everyone running AIX would be liable for infringment (hoping to make IBM's customers nervous, so they would put pressure on IBM to settle quickly and out-of-court)

    Further speculation:
    9: ???
    10: IBM will buy SCO at an inflated price just to shut them up
    11: PROFIT!!!! for SCO lawyers and executives

    To further condense:
    It's a publicity stunt, SCO wants a buyout. They're targeting IBM because they IBM has lots of money, whereas no Linux-based companies are making a profit.

    --
    0 1 - just my two bits
  12. A real-world DoS attack... by chundo · · Score: 5, Interesting

    Time for everybody to sue SCO for previous GPL violations! That'll keep their lawyers tied up for awhile.

    -j

  13. Re:On dear Lord by bobtheheadless · · Score: 5, Interesting

    I do find it interesting that Windows "Server" 2003 release and advertising coincides with this whole battle though...

    Worried about the uncertainty of AIX and Linux? Good thing we here at M$ have a great solution for you...

    --
    --- If I had a funny sig too, you might be laughing now.
  14. Re:Not filed for tempoary injunction!!! by RocketScientist · · Score: 4, Interesting

    And typically the company asking for the injunction has to put up a bond in the event that they lose the case. It'll be interesting to see SCO, a company with little cash reserves that's been operating in the red come up with that kind of cash.

  15. Re:don't miss the McBride interview... by the+melon · · Score: 5, Interesting

    Aparently he is not that good at math either....

    "--if you look at the marketplace over the last two years, there've been 2 million servers shipped into the market. Our UnixWare price tag of $1,500 would have generated $3.5 billion in revenue for us."

    By my count that would be 3 billion if they had a 100% market share. But considering their share is about 2%, from all the numbers I have read, that would leave them with a rather generous $6 million.

  16. Re:Future licenses by ajs · · Score: 5, Interesting
    Ok, IANALBIJTTO (I am not a lawyer, but I just talked to one) about this, and here's the scoop, which is kind of obvious if you think about it:

    SCO can do this if, and only if
    • They own the original rights
    • They have allowed for revocation in the license
    • They have allowed for revocation of any and all sub-licenses in the agreement as well
    So, you see the mold is already cast here. It's all in the license, and who owns the rights. The question is, what are the exact terms of the license, and can IBM get out of those terms on the basis of the capricious damage to their business or other grounds?

    I'm not a lawyer, this is a lawyer friend't assesment based on very little info and then translated through me, so take it with a grain of salt. But I think the general idea that SCO could not revoke the sub-licenses due to the damage to the market (as someone suggested) would be kind of moot, since SCO only has to demonstrate that THIS agreement allows such. Of course, IBM would be foolish to have allowed such a thing....
  17. Re:Another URL by Jeff+Kelly · · Score: 5, Interesting
    If you purchase software, and you accept the license (usually by opening the shrinkwrap or the CD case), you are bound to all its terms
    This might be the case in the United States. Here in Germany (and in many other countries which have adopted similar law) you are not bound to those shrinkwrap licenses since you see them only after you have already bought the software.

    If you make additions to a contract (and EULAs are such additions according to german law) both parties have to be able to see those additions before the contract is placed. Since this is rather seldom the case for EULAs these licenses are not even worth the paper they are printed on.

    Regards Christian

  18. Possible good outcomes. by Frobnicator · · Score: 4, Interesting
    This has the potential to be a good thing for everybody.

    We need to find the actual injunction (I haven't found it yet) and actually read the thing, and as such this is purely speculative, but it opens up a nice posibility.

    In the long run, the judge *must* find for or against the complaint, dismiss the complaint, or remand it to a higher court. It appears (although nobody seems to have the actual complaint) that the complaint is two parts. The first is that they used the code in Linux, and the second is that they are now distributing AIX without a licence to SCO's code. That second point is the one they would file the injunction on.

    This boils down to a simple complaint: "We terminated their license, so they must stop using our property." If that were the entire complaint in the injunction, the judge would have to agree since the Supreme Court has upheld that rights of property owners is one of the key elements of freedom. Not being able to use your property is the loss of freedom.

    That complaint is so fundamental that he could not simply dismiss the complaint. He therefore must rule on it, or the law, or remand it up the chain of command.

    The judge could rule that SCO is correct, meaning that:

    1. Property rights were not permanently transferred, nor need they be transfered with an IP license, therefore...
    2. IBM must pay SCO forever or until it changes its code because...
    3. The US Government, military, and big business currently depend so much on AIX and...
    4. Forcing all government and business entities to stop using AIX would endanger lives and the economy.
    5. And if the Government couldn't get newer AIX versions, billions or even trillions must be urgently spent on computer equipment and programming...
    6. Meaning that the penalty is an indirect, but severe, penalty against the Government, military, and the economy generally.
    7. In addition, since some have claimed that nearly all other OS's may be at risk, it presents a huge danger for basically everyone (except Sun, and perhaps Microsoft who just got a licence... Hmmm...)

    By ruling FOR SCO, the judge would not only put a penalty on IBM, but on everyone who uses it. While the simple case (no pay, no play) is reasonable, IBM's lawyers could easily argue that the damage to society and possible lives lost would outweigh SCO's property rights.

    Ruling FOR SCO would set a precedent that Microsoft and others could quickly follow -- Revoke the licenses to each version of Office even faster, or include in new online music services a quickly expiring license. When the song goes popular, the license expires, and you must pay the new, higher rate. It would be extortion, except the SCO case would make it legal.

    Conversely, he could be ruling that you *CAN* continue to use IP after terminating your license. This would have profound effects (I like some of them), including...

    1. Property rights are transferred forever when licenced, therefore...
    2. Sales contracts of software and IP are binding and perpetual, therefore...
    3. Companies cannot ever revoke rights to licenced IP, therefore...
    4. Resold licences allow the seller to keep the licenses, and ...
    5. Since there is no minimum cost to resell or transfer IP rights...
    6. Huge holes would be introduced in IP law. Would that mean that we can all buy and burn the latest software / music / movies at no cost from our friends?

    That can't happen either. The sectors of our economy dealing with IP would be blown away, and that would also have so profound negative effects that the judge could not rule that way.

    So either way the judge rules in the end, he cannot justify the expense to society of ruling for or against them. A judge at the state level sould not put the entire nation's economy into such a state. That would mean he should remand the case to a higher level. The district cour

    --
    //TODO: Think of witty sig statement