Slashdot Mirror


IBM Denies Charges of Unix Theft

ahooton writes "C|net is reporting that SCO has filed a lawsuit accusing IBM of theft of it's Unix intellectual property. SCO alleges this occurred because IBM released portions of the Unix system, owned by SCO, in to Linux." While the suit is nothing new, IBM's retort is. IBM asserts it is innocent of any charges of wrongdoing. Additionally, IBM is accusing SCO of trying to stifle Linux development through the use of the courts.

35 of 400 comments (clear)

  1. REAL Purpose by kkirk007 · · Score: 5, Insightful

    I know it's been said before, but...
    SCO's real purpose behind this lawsuit is not to get money, but to publicize itself in hopes of finding a larger company to buy them.
    SCO's business hasn't been so great lately, and...they're just a little desperate at this point.

    1. Re:REAL Purpose by BrokenHalo · · Score: 4, Insightful
      SCO's business hasn't been so great lately

      Maybe it would be if they put the same effort into producing a worthwhile actual product that they waste on fishing trips in the courts.

    2. Re:REAL Purpose by 0x0d0a · · Score: 4, Informative

      Doesn't really mean anything. You could have a company with each share not valued as much but with many shares issued, or with few shares but each share valued highly.

      Market capitalization is much more useful:

      IBM:
      Market Capitalization $147.9B

      Caldera International:
      Market Capitalization $40.2M

      (Yahoo Quotes)

    3. Re:REAL Purpose by mpsmps · · Score: 4, Insightful

      It would be suicide for IBM to buy them. If they did, every failing tech company would see how SCO made millions out of nothing, and their boards would insist on suing IBM for patent infringement in hope of getting bought out. IBM has to show that companies will regret bringing patent lawsuits against them.

  2. Released or reimplemented? by Max+Romantschuk · · Score: 4, Insightful

    SCO alleges this occurred because IBM released portions of the Unix system, owned by SCO, in to Linux.

    I've understood that they've reimplemented some technology in Linux, but have they really just taken the existing pieces and put them into Linux? I doubt it.

    Would someone care to shed some light on the subject?

    --
    .: Max Romantschuk :: http://max.romantschuk.fi/
    1. Re:Released or reimplemented? by Anonymous Coward · · Score: 5, Informative

      While IBM has incorporated some of their code into Linux, none if it has been from SCO.

      IBM's operating system, AIX, has some code from SysV, for which SCO owns rights, but the code they've ported to Linux (such as JFS) are property of IBM.

      SCO is probably trying to muddy the issues - because AIX contains both code that has been shared with Linux and code that SCO owns rights to.

      However, considering that SCO has never specifically pointed out what parts of IBM's contributions to Linux supposedly violate their agreements, they have zero credibility.

  3. What I hope this means by OverlordQ · · Score: 4, Insightful

    What I hope this means, is that IBM will once and for-all put an end to this SCO FUD. Who knows the true reason behind SCO's logic, but whatever it is, we dont need it ;)

    --
    Your hair look like poop, Bob! - Wanker.
    1. Re:What I hope this means by arvindn · · Score: 4, Interesting
      What I hope this means, is that IBM will once and for-all put an end to this SCO FUD.

      There's exactly one way IBM can do that: buy SCO. Sco/Caldera's logic is simple: they are a dying company, and they know it. So they want to make it as nasty as possible. If this gets to court, SCO doesn't have a whit of a chance (which is why they didn't go after the little fish first, BTW.) However, it might be the end of SCO, but it will be very costly in terms of PR for IBM as well. SCO's hope is that IBM will find buying SCO to be the easier way out. That's the best case scenario for them.

      BUT. That would put an end to SCO FUD, but MS FUD will start right thereafter. (See, we've been saying it all along, linux is incapable of innovation, sco was going to prove that in court, but big baddie IBM was afraid of them and bought them out.) So its a lose-lose situation.

    2. Re:What I hope this means by jbolden · · Score: 4, Interesting

      They would still have to go to court. SCO does not intend to survive the lawsuit. The real issue IMHO is whether SCO execs have actually crossed the line into fraud considering how untrue some of the statement in the original were.

      IANAL but it sure sounds like lying under oath to me.

  4. I know that there isn't SCO code in Linux because by DanThe1Man · · Score: 5, Funny

    ....LINUX DOSN'T SUCK!!

  5. Well, if there is one GOOD thing I can say... by Tokerat · · Score: 4, Interesting


    ...it's "At Least SCO went after the big guys first."

    There is no RIAA-suing-college-kids style lawsuit here. They went right after someone who could afford to defend themselves, instead of trashing say, SuSe and RedHat.

    On the other hand, it's IBM, who probably even has a patent on human life for christ sakes. Therefore I doubt we'll be seeing much more of SCO, especially if this suit doesn't hold water.

    --
    CAn'T CompreHend SARcaSm?
    1. Re:Well, if there is one GOOD thing I can say... by Guppy06 · · Score: 4, Insightful

      "There is no RIAA-suing-college-kids style lawsuit here."

      That's because the RIAA is looking to use fear tactics to shut down competing media delivery forms. SCO is just in it for the money, and it's over at IBM.

  6. Code Red for Open Source? by Anonymous Coward · · Score: 5, Interesting
    Here's another CNET article about the suit. It makes it clear that SCO is trying to make pure FUD:
    McBride refused to detail which specific code had been copied but said there were several instances--"some of them go back several years, and others are recent"--and said the copying was "not minor." SCO, however, won't publish what it's found.

    "We feel very good about the evidence that is going to show up in court. We will be happy to show the evidence we have at the appropriate time in a court setting," McBride said. "The Linux community would have me publish it now, (so they can have it) laundered by the time we can get to a court hearing. That's not the way we're going to go."

    Next he'll tell us there's weapons of mass destruction in the Linux code and the fact we can't find them just shows how diabolically clever the people who hid them were. Send the UN inspectors!
    1. Re:Code Red for Open Source? by Anonymous Coward · · Score: 5, Insightful

      This allegation really underscores a primary issue of closed source software - it's not out for public review, and hence, it would be VERY difficult to validate these claims. For all we know, SCO's code is a rip-off of Linux or some prior open-source code that Linux was a beneficiary of. SCO never published their source and there's nothing outside of SCO (or maybe IBM, if there was some kind of agreement) to validate the claims. The trouble is, we can trust neither of those parties to present untainted copies of the relevant code as both could have altered timestamps or copied in code. There's also the fact that some processes in software can just really be done in one optimum way.

      This is a good reason software should not be considered "published", hence copyrightable, unless the source code exists in some human-readable means in some organization outside of the "software publisher" (who truly publishes nothing), a place the courts could seriously look at as proof of the existance.

      A way that might serve as a valid stopgap would be the generation of an MD5 hash of each source file and submitting that to some trusted agency (Library of congress?) for another digital signature and timestamp to be added, proving the date of creation to some legal standard so that these allegations could be backed with proof. We'd know the plaintext was validly signed by the LOC and that it existed at the time alleged to.

  7. Linux: IBM's true universal adapter by Thaidog · · Score: 5, Interesting

    The good thing is that right now you can run linux on IBM's zSeries, AS/400, RISC6000,... all the way down to a PDA. It's no joke to say that there is alot of money about to be made... That's the real reasonb for this suit...

    --

    ||| I still can't believe Parkay's not butter.

  8. More News... by KoolDude · · Score: 4, Insightful


    Here is another CNet article on what SCO Group Chief Executive Darl McBride thinks on this issue. From the article,

    "We're finding...cases where there is line-by-line code in the Linux kernel that is matching up to our UnixWare code," McBride said in an interview

    Interesting... eh? :)

    --
    getSexySig(); /* returns sexy signature */
    1. Re:More News... by Ami+Ganguli · · Score: 4, Insightful

      Yeah, I thought that was interesting too. Given the limited availability of SCO code, I can think of two explanations that are much more likely:

      • both SCO and Linux developers studied the BSD code
      • the SCO code was (perhaps accidentally) stolen from Linux

      Anyway, if I had discovered that my proprietary software product contained GPL code, I'd discretely try to replace my code, since I'd have much more to lose from legal action. If somebody can prove that SCO stole GPL code, it might be possible to force them to GPL their entire kernel.

      --
      It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail. - Abraham Maslow
    2. Re:More News... by geschild · · Score: 5, Interesting

      Now there's a defence worth contemplating: it's far easier to prove beyond a reasonable doubt that certain code existed in Linux at some point in time than it is to prove the same for a closed pieces of software. This works both ways: the closed source owners can show it was in an open source repository but will they be able to prove it was in their repository before that?

      There's an oportunity for a countersuit based on breaking the GPL in there somewhere...

      --
      Karma? What's that again?
  9. UNIX license buyouts ? by mj01nir · · Score: 4, Interesting

    From a different CNet article about the lawsuit:

    "HP did a complete buyout of Unix licensing from SCO," HP spokesman Brian Garabedian said. "We have a perpetual license rather than per copy license for HP-UX...We don't believe we have any exposure to the SCO lawsuit."

    Sun, too, bought out its Unix license, said John Loiacono, vice president of Sun's operating platforms group.

    "We bought our Unix license out....We are unencumbered for all things," including Sun's version of Linux, he said.

    And then in the linked article:

    IBM did make one argument defending its use of Unix intellectual property, saying it has the "irrevocable, fully paid-up and perpetual right to use the 'proprietary software' that it is alleged to have misappropriated or misused."

    It sounds like IBM believes that they have "bought out" its license as well. So ...:

    1) Did SCO mislead IBM (and possibly HP, Sun, etc) with these license buyouts?
    2) Is SCO trying to make everyone forget about the license buyouts?
    3) Does SCO consider the buyouts invalid for some reason?

    The whole thing is just weird. SCO is done. Even if they win, no one will ever trust them again. They could produce an OS that whipped any commercial or OSS implementation, but no one would buy it. Had they attacked a smaller, but significant target first (Sun?) they might have had a chance at getting bought out. But with IBM, I don't think they will bother, they'll just crush SCO. They have unfathomable resources. IBM could even afford to lose the case. Sun couldn't.

    --
    the no .sig .sig
  10. Feh. by BJH · · Score: 5, Insightful


    Has anyone else seen the comments McBride has been making lately? Here's some choice quotes from news.com.com.com.com's unbiased and uninflammatory article, "Code Red for open source?":

    "We're finding...cases where there is line-by-line code in the Linux kernel that is matching up to our UnixWare code," McBride said in an interview.

    Please note that he has refused to release examples of this.

    In addition, he said, "We're finding code that looks likes it's been obfuscated to make it look like it wasn't UnixWare code--but it was."

    Please note that he has also refused to release examples of this, too.

    "The Linux community would have me publish it now, (so they can have it) laundered by the time we can get to a court hearing. That's not the way we're going to go."

    Yeah, that's a great excuse to not actually give any evidence of the accusations you're making - tell people that 'the Linux community' will try and sanitize every existing copy of the source code to all the versions of the kernel containing this supposed SCO source - which, he says, has been in the kernel for 'several years'! Perhaps he missed the bit where his lawyers briefed him on the GPL and how it lets anybody have a copy of the source code - including SCO itself! Is he really suggesting that SCO lacks the ability to keep a copy of all currently extant versions of the Linux kernel to use as evidence? F'chrissakes, the md5 checksums of Linus's kernels are public knowledge - if anybody tried to 'sanitize' a particular version, it'd be ridiculously easy to prove that it'd been changed since its original release.

    "This is not about 10 lines of code, it's about 20 years of extremely valuable intellectual property we're trying to protect...Am I supposed to lie down and not say anything about it?" McBride said. "There's a certain point here where you stand up for what's right and let the chips fall where they will."

    Gotta love that last line... McBride wouldn't know "what's right" if it came up and bit his ass.

    I can't even begin to express my disgust for a company that insults, intimidates and sues the very people who have made it possible for SCO to distribute their own version of Linux. Crawl away and disappear, McBride - you're a liar and you know it.

  11. Any evidence yet? by FFtrDale · · Score: 5, Insightful

    Last I heard, IBM was asking SCO to state specifically what code they were alleging that IBM had used, and IBM had gotten no answer. Today's story still has IBM describing SCO's allegations as "unsupported." If the nice folks at SCO can't back up their claims, are they just betting that the effect of the news stories on their business ("no bad publicity") will be greater than the losses they'll take for filing a frivolous lawsuit? What am I missing here?

    --
    Think, write, think, edit, think...then post.
  12. Re:Unix code copied into Linux alleged by Tokerat · · Score: 4, Funny


    ...McBride then stated "Clearly you can see places where IBM's source code adds two numbers together, in some instances the same two numers our software would be adding durring the same process. This is clearly infringment." McBride was scheduled to answer more questions after the laughter died down, but was apparently then unavailible for comment.

    --
    CAn'T CompreHend SARcaSm?
  13. And might as well add... by zurab · · Score: 4, Informative

    That there is the SCO reply saying that they have hired consultants and found major code duplications between UnixWare and Linux, although they will not release the information about what parts of code they are talking about that has been duplicated. Article also quotes SCO's Darl McBride:

    "We feel very good about the evidence that is going to show up in court. We will be happy to show the evidence we have at the appropriate time in a court setting."

    I hope they are bluffing, or IBM will just buy SCO out and be done with it.

  14. IBM and Linux Shall Pay! by f0rt0r · · Score: 5, Funny

    I found the code that matches up exactly, the top five matches are ( drum roll )

    5) for ( int x=0;x lt 10;x++)
    4) while ( x lt 10 ) {
    3) #include stdio.h
    2) #include math.h
    1) int main( String args[] )

    Number 1) shows up in every .cpp file! Linux developers will pay for this blatant violation of SCO's IP rights!

    Note: for some reason the board wigged out with greater than and less than signes, so I had to leave those out. lt = less than

    --
    I can't afford a sig!
    1. Re:IBM and Linux Shall Pay! by localghost · · Score: 4, Funny

      None of those show up in my C++ code.

      for 5, I use "for (int x=0;x<10;x++)" (I removed spaces)
      for 4, I use "while (x<10)" (spaces again)
      for 3, I use "#include <stdio.h>" (yours will produce an error)
      for 2, I use "#include <math.h>" (again, error)
      for 1, I use "int main(int argc, char *argv[])" (I've never seen the syntax you used)

      Oh, and to make the < sign, you need to escape it with "&lt;".

  15. Possible community response? by Viv · · Score: 5, Interesting

    Out of curiousity, has anyone ever considered the possibility of a group of people individually filing a claim in small claims court against a company that is doing something they don't like?

    In this case, for example, what if we could mobilize a few thousand people who use Linux professionally to sue SCO for slander? Professionals who use Linux are risking their reputation on it; SCO saying that Linux uses stolen code reflects badly on the professional. If what SCO is saying is untrue, that's slander and is in fact causing damages, yes?

    Now, here's the trick -- if 5000 professionals who are effected by this in the USA were to file claims in small claims court of say, $1000, then SCO would have to simultaneously defend 5000 cases, or risk losing $5 million in damages.

    What kind of effect do you think that would have on a company of SCO's size? Catastrophic, I'd think. And what's nice is that since they're impuning our professional judgment without providing any truth, we should have a cause of action.

    If this is doable, this could be a serious way for a large community such as the free software community to show extreme displeasure with companies that do stuff like this, and for it to really count.

    Any lawyers or anyone with professional knowledge out there that can comment?

    1. Re:Possible community response? by geekoid · · Score: 4, Funny

      what are you, a christian scientist?

      yes, that WAS funny, and if you don't understand it, don't mod it.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  16. Just posted to LKML by rf0 · · Score: 4, Interesting

    "As somone who walked for SCO (or rather Caldera how it was called at that
    time) I can tell you this is utter crap. There were very people actually
    doing Linux kernel work then (and when the German office was closed down
    all those left the company) and we really had better things to do then
    trying to retrofit UnixWare code into the linux kenrel. Especially given
    that the kernel internals are so different that you'd need a big glue
    layer to actually make it work and you can guess how that would be
    ripped apart in a usual lkml review :)

    It might be more interesting to look for stolen Linux code in Unixware,
    I'd suggest with the support for a very well known Linux fileystem in
    the Linux compat addon product for UnixWare.."

    Could be intresting :)

    Rus

  17. Rowboat vs. Bizmarck by Akardam · · Score: 4, Funny

    McBride's taking a dingy up against the battleship that is IBM. Can he honestly think that SCO won't be reduced to so much virtual matchwood? I'm just waiting for the moment when he's staring down IBM's big guns, and goes "Eep!".

    Wait for it...

  18. Comments from an ex-Calder employee` by ssimpson · · Score: 4, Insightful

    I like Christoph Hellwig's (ex-Caldera employee) comments on the Linux Kernel Mailing List 02 May 2003 06:44, in part:

    "It might be more interesting to look for stolen Linux code in Unixware, I'd suggest with the support for a very well known Linux fileystem in the Linux compat addon product for UnixWare.."

    Let's hope the FSF sue SCO for infringement of the GPL. For a billion dollars. I'm sure IBM lawyers would lend a helping hand! ;)

    --
    "Mary had a crypto key, she kept it in escrow, and everything that Mary said, the Feds were sure to know."
  19. Barratry by shepd · · Score: 5, Informative

    I'm pretty sure any lawyer that helped you with this would be charged with barratry, or for vexatious litigation.

    I'm not sure if individuals can be charged with something similar. You'd have to look it up. :)

    Note that the charges you are laying can still have some merit, but doing them in an attempt to subdue the defence isn't legal.

    --
    If you could be told what you can see or read, then it follows that you could be told what to say or think - BoC
  20. So, what if SCO is right? by akorvemaker · · Score: 5, Interesting

    Just curious. It seems that all the comments revolve around how SCO is stupid and wrong and greedy and dumb and soon to be extinct.

    What if they're not. What if they do have a genuine grievance. I'm not trying to be a troll or flamebait, just honestly curious. What impact would this have on GNU/Linux? Would people honor SCO's claims if they're proven right?

  21. Very confusing! by minkwe · · Score: 4, Interesting
    "We're finding...cases where there is line-by-line code in the Linux kernel that is matching up to our UnixWare code," McBride said in an interview.

    "In an e-mail discussion that took place 24 and 25 April, SCO-Caldera Senior Vice President Chris Sontag told MozillaQuest Magazine that there is SCO-owned code in Red Hat and SuSE Linux distributions. He also told MozillaQuest Magazine that the tainted code is not in the Linux kernel that Linus [Torvalds] and others have helped develop. We're talking about what's on the periphery of the Linux kernel.

    --
    "Fighting terrorists with millitary might is like killing a mosquitor on your Dad's forehead with a rifle."
  22. IBM's Open Source Guidelines by scottme · · Score: 5, Informative
    IBM has a comprehensive and stricly-enforced internal set of guidelines that any employee who works on OSS projects, whether on IBM's time or on his/her own time, must read, understand, and certify compliance with. It's a condition of employment, even. And there's an approval process that must be used (and I quote):
    whenever an IBM group wants to:
    • start or join an OSS project with the intention of contributing code to the project and/or maintaining the code base;
    • include third party OSS with an IBM product or service;
    • ship some or all of an IBM product in source code form under an open source license;
    • publish the source code for a reference implementation.


    IANAL, but it seems to me that there must be a defensive line against the SCO suit in the mere fact that it has promulgated that policy. Of course the existence of the policy is no guarantee that it is going to be adhered to 100%, but in the (unlikely) event that SCO is able to establish that some illegal copying of their material did take place, the corporation can hold its hands up and ask what more it could have done to prevent it.
  23. Re:Ballmer Misquoted by Surak · · Score: 4, Informative

    Ballmer actually said: "customers will never really know who stands behind this product."

    The intent is similar, but it's a subtler shade of meaning here.

    Of course, people pay Red Hat and IBM and other companies money to stand behind the code. And you DO know who wrote the code anyways. Their names are all over it.