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.

30 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 Anonymous Coward · · Score: 3, Insightful

      I think the bottom of the CNET page explains your point best

      Related Quotes [stock quotes]

      Intl Bus. Machine
      85.89

      Caldera Intl
      3.69

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

    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.

    4. Re:REAL Purpose by martyn+s · · Score: 2, Insightful

      Well, yes, much more starkly. Just as another example:

      Microsoft: 25.94
      Amazon: 28.88

      Stock price usually has nothing to do with it.

  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/
  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.
  4. 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 ultrabot · · Score: 2, Insightful

      "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

      What's also interesting, is that since SCO has shipped Linux kernel, they are accepting that it is ok. So if this hypothetical code exists, they gave it away.

      I also wish to enclose the obligatory "fuck off and die, SCO", now that we are on the topic.

      --
      Save your wrists today - switch to Dvorak
    3. Re:More News... by SN74S181 · · Score: 2, Insightful

      The theory is that SCO shipped Linux kernel with the infracting code in it, so now they magically can't own that code, even though they weren't the party that put the infracting code in. But if they were unaware at the time that the infracting code was in it, it's ludicrous to claim they suddenly have surrendered portions of their code base.

      People really need to be careful regarding logical handwaving tricks like that. There are PHBs out there who might actually believe your theories; they'll pitch ALL GPL code out of their shops and set up quarentines if that is the case. It certainly doesn't make the case for a business friendly Open Source process.

      Do you seriously think Programmer G at Company D can slip a little code from Company E into a GPL product that Company E also contributes to and Company E is going to surrender their code base to the FSF?

      If so, stand over there so the rest of us can snicker at you.

    4. Re:More News... by nathanh · · Score: 3, Insightful

      "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? :)

      Not just interesting. It's bloody hilarious! The reasonable conclusion is not that Linux has appropriated SCO code, but rather that SCO has appropriated Linux code. This means McBride is about to demonstrate - in a court of law - that SCO violated the GPL. What a maroon!

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

    1. Re:Feh. by Anonymous Coward · · Score: 2, Insightful

      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.

      This is such a bonehead statement, I blinked twice when I read it. After all, Linux being open source, every revision of the source code is readily available. You could not simply "launder" this away unless you somehow manage to destroy every source code distribution of linux in existence that has ever been burned onto a CD, backed up onto tape, etc etc.

      If the allegations have any basis, SCO has no reason not to disclose the details.

  6. 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.
    1. Re:Any evidence yet? by Anonymous Coward · · Score: 1, Insightful

      Well if I was a SCO executive with a heap of stock options that I had no doubt voted to pay myself, i'd be looking into getting the old SCO stock price up before I did the sell thing.

      "Hmmm, if we sue IBM for a HEAP of cash, then even if we don't win the stack of cash, there are likely to be enough prospectors who think we might that they'll start buying up our currently 'cheap-as-chips' shares and I can sell mine off and get off this sinking ship."

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

  8. Re:Code Red for Open Source? by SiliconJesus101 · · Score: 3, Insightful
    "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."

    Unbelievable!! So this guy doesn't even want the issue resolved??? I guess it's true that they are simply trolling for dollars in the form of a quick settlement or buyout.

    As far as I understand it, don't the attorneys on both sides have to share the information they have regarding the lawsuit??

    --

    "The strong will do what they want, the weak will do what they must."
    -Thucydides

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

  10. Yeah! by rsilvergun · · Score: 2, Insightful

    IBM's gonna defend Linux. This was the only thing I was worried about, that IBM would cut a deal with SCO and leave linux users out in the cold. Now that IBM's going to defend itself (and by extention linux) SCO is pretty much done for. I'm really looking forward to that company going bankrupt after what they said about Redhat and Suse.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
  11. It's a marketing ploy by n_jed · · Score: 1, Insightful
    An attempt to get all the linux advocates on its side...

    IBM is accusing SCO of trying to stifle Linux development through the use of the courts

  12. 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."
  13. Re:Cheap trik. by SN74S181 · · Score: 2, Insightful

    Ok - so you've unix' IP, so what ? What have you done with it. Hybernate and wait for unix to hatch by itself and pour money on you. Come on...

    Sounds like exactly what Ray Noorda did with the DR-DOS code base. He bought it solely as a vehicle to sue Microsoft. But that was against Microsoft, so a whole lot of you guys were cheering him on.

  14. Re:Possible community response? by joonasl · · Score: 3, Insightful

    How truly uniquely American response to basically everything: "Let's sue!!". :)

    --
    "There is a terrorist behind every bush"
  15. Then make it a "lose-lose-lose" situation for all by Taco+Cowboy · · Score: 1, Insightful


    Sadly, the MS FUD has already started. In the wonderfully written "Code Red for Open Source" article at Cnet which is fair and balanced (in that Fox News kind of way) Balmer is quoted as saying something to the effect, "See, you dont know who's writing your OSS software."



    If MS wants to make it a "lose-lose" situation for the IBM-Linux alliance, then we can make it a "lose-lose-lose" situation where NOBODY came out a winner.

    Steve Ballmer may thinks he owns the world, but he ain't, at least not yet.

    Believe it or not, MS still depend on the world for its own survival, Mr. Ballmer may think otherwise, but if MS crosses the line, the world will shuns MS like a plague.

    No one is an island in this world, MS is no exception. If MS really wants a fight, then lets make it one that MS wins nothing but financial ruins.

    MS is already suffering from utter Moral Bankrupcy, and from there it's a very short trip to Financial Bankrupcy.

    IBM has learnt the bitter lesson back in the 80's, mebbe it's MS turn this time around.







    --
    Muchas Gracias, Señor Edward Snowden !
  16. Re:Code Red for Open Source? by Goonie · · Score: 2, Insightful
    "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."

    Is he arguing the "linux community" is somehow going to make millions of copies of older versions of the kernel source on the various squillions of CD-ROM's out there disppear so SCO can't prove its case? Or is he worried that any piece of code allegedly pinched from UnixWare can have its functionality duplicated so quickly that the arguments about Linux the bicycle are disproven? Either way, it's entirely ludicrous.

    --

    Any sufficiently advanced technology is indistinguishable from a rigged demo
    --Andy Finkel (J. Klass?)
  17. Re:Unix code copied into Linux alleged by Anonymous Coward · · Score: 1, Insightful

    What, you mean that they'll go back in time and stop themselves posting the patchs to the LKM? McBride is a fucking loony if he thinks anyone is taking this seriously.

  18. Re:IBM and Linux Shall Pay! by zonix · · Score: 2, Insightful
    None of those show up in my C++ code.

    BTW, isn't the kernel written in C?

    --
    What would an EWOULDBLOCK block, if an EWOULDBLOCK could block would? -- me
  19. Open source patent licenses? by Anonymous Coward · · Score: 1, Insightful

    I doubt that open source would be completely abandoned. It would be a serious blow to the momentum of open source. And it would be a very long time before businesses would trust open source again.

    This issue is going to fuel the calls for open source patent licensing. I've seen it suggested several times before right here on Slashdot. Basically, a patent holder would license software patents for use in open source software. They could be used commercially in exchange for cross-licensing of other patents on on the same terms. It would effectively immunize open source projects against patent infringement suits. The first company to sue a big open source project over a patent would risk a countersuit on the patents of several different patent holders. As soon as they sue, they've violated the terms of the license, which requires open source cross-licensing.

  20. Re:Ballmer Misquoted by tigheig · · Score: 2, Insightful

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

    The EULA's that I've seen for most commercial software products (including Microsoft's) clearly state that they're not guaranteed to do anything, and are not guaranteed to not harm your system or you. It seems quite clear that the difference in this area between commercial OS/software releases and Open Source is that, with Open Source you never know who will stand behind the product, and with commercial software you will know that nobody stands behind the product.

    At least with the former I have a chance that someone, somewhere will stand behind their product.