Slashdot Mirror


SCO Amends Suit, Clarifies "Violations", Triples Damages

Bootsy Collins writes "This evening on C|Net contains three new items. First, they've upped the damages they're seeking to $3 billion. Second, they claim that by making SMP technology generally available through Linux, IBM violated federal export controls and thus breached their contract with SCO through committing an illegal act. Finally, they elaborate on one specific technology they claim rights to which IBM inserted into the 2.5 kernel series -- the read-copy update memory management features which went in at 2.5.43. Unclear is why SCO thinks they have the rights to RCU, since the technology was originally developed by Sequent in the early 1990s."

108 of 1,347 comments (clear)

  1. They must really be scared now. by rkz · · Score: 4, Interesting

    They sound like a crazy old drunk, making up more and more unsubstanciated cliams, C|Net's article sounds like their getting tired off this too.

    1. Re:They must really be scared now. by Anonymous Coward · · Score: 4, Funny

      Yeah no shit. I'm awaiting the day that SCO claims that Osama himself has submitted patches to the kernel and that Alan Cox colaborated with Saddam Hussain in the mid 90's.

      Admittedly, I wouldn't mind seeing D'ohl McBride stood in a street corner shouting idiotic nonsense at passers by. At least then his actions would be socialy unacceptable and the authorities could lock him up. It seems that it is perfectly O.K to act like a paranoid loon if you're a CEO and your conspiricy theories are printed in an international news outlet. Then its O.K

      If you were an SCO employee, would you feel at least a little concerned that your boss is aparently dilusional? I know I would.

    2. Re:They must really be scared now. by Forge · · Score: 5, Interesting

      Pore SCO. The funny thing is that "someone" has demonstraighted a major comitment to Linux by steping forward to pay Dr. Torvalds a full time salary to work on just the kernel with no obligations to any specific vendor etc...

      My gues ? It has something to do with SCO's silly little lawsuite. See the story before this one.

      Now here is the tall order SCO has to fill to compleat this case.

      1: These specific lines were introduced into the Linux Kernel by IBM at this date.

      2: That date must be after the comensment of Trilian.

      3: That item was not in any IBM product before Trilian.

      4: That item was not in BSD.

      5: And finaly. That item was in SCO before the Trilian project.

      That's a lot to prove and I doubt SCO will ever do it.

      --
      --= Isn't it surprising how badly I spell ?
    3. Re:They must really be scared now. by BroncoInCalifornia · · Score: 5, Insightful

      I do not think they are serious about the lawsuit. SCO is serious about making a lot of noise.

      IBM did not offer to buy them. So SCO will try to raise the noise level some more.

      But now all they can do is sound like the Iraqi disinformation minister.

      "Those penquins are infidels. There is no way penguins can write SMP code without our help. We will slaughter all the penquins and have them for dinner"

      --

      Religion is the main cause of atheism.

    4. Re:They must really be scared now. by rjamestaylor · · Score: 5, Interesting
      Crazy drunk or like my three year old testing his limits. Their claims are so egregious and far-reaching that they're threatening everyone except Sun (wonder who that "mystery licensee" was?) -- including a not-so-veiled threat against Microsoft for Windows. And I did see that Cringley (at Infoworld) is rumor-porting AT&T may weigh in against SCO.

      My [large hardware company] rep who is supplying me with neat technology including handhelds, laptops, tablets and Linux server appliances, is also the rep for SCO. He tells me he doesn't even want to touch SCO now that they've pulled their shenanigans. He even referenced McBride's comment that contracts are strong bases for lawsuits as a real chiller. Imagine being so reviled that sales people don't want your money...

      I wonder if employees of SCO have any pride left, or any intention on working with the tech industry again? They may not be the source of SCO's vitrol and venom, but as long as they sit quietly and let the day traders pimp and pump the stock they are one and the same as McBride/Sontag/et al. We need a hacker revolt from within SCO -- if any are left. ... Until proven otherwise, no friends of tech or Open Source remain in SCO.

      If you work for SCO you better cut your ties with Sontag/McBride or lie on your resume for your next position. Pretending to be unemployed since Caldera brought on McBride will get you further than admitting you sat idly by while your company pulled the crap that it is pulling.

      --
      -- @rjamestaylor on Ello
    5. Re:They must really be scared now. by Anonymous Coward · · Score: 5, Insightful
      My [large hardware company] rep who is supplying me with neat technology including handhelds, laptops, tablets and Linux server appliances, is also the rep for SCO. He tells me he doesn't even want to touch SCO now that they've pulled their shenanigans.
      Yeah, that's what he tells you. He'll be telling his SCO clients how he doesn't want to touch Linux now it's potentially contaminated.
    6. Re:They must really be scared now. by micromoog · · Score: 4, Insightful
      If you were an SCO employee, would you feel at least a little concerned that your boss is aparently dilusional? I know I would.

      Not necessarily delusional, just driven by the same pathological greed that drives many corporations. Try it this way:

      "If you were an SCO employee, would you feel at least a little concerned that your boss is aparently driven by the same pathological greed that drives many corporations such as Enron and WorldCom into the ground? I know I would."

    7. Re:They must really be scared now. by epiphani · · Score: 5, Insightful

      I personally think that this is SCO trying to get IBM to buy them out. Trying Violently.

      Think about it - SCO's buisness model is failing because of Linux and Open Source. Claiming 3 Billion Dollars in Damage is probably a good way to get IBM to buy them out - because why spend the money on fighting the lawsuit or paying a settlement - buy out SCO, problem goes away, and all that "incredibly valuble" unix code can be dumped into linux, where useful.

      My Theory...

      --
      .
    8. Re:They must really be scared now. by sjvn · · Score: 4, Insightful

      Yes, there are many Mormons in Utah so many of them who are technically inclined work for Utah tech. companies. That said, I've known many of them for more than a decade at WordPerfect, Novell, Caldera/SCO and dozens of other companies and they're no more inclined to blindly obey a CEO than a Roman Catholic is to obey his CEO because he's been taught that the Pope in infalliable.

      For example, I know for a fact that many current and former Caldera/SCO employees *hate* what their company is doing. Why don't you hear more from them? Because they have mortgages to pay, childern to feed and they don't want to lose their jobs and/or find themselves sued left, right and sideways. In short, they're people like everyone else trying to get by as best they can.

      Steven

    9. Re:They must really be scared now. by vladkrupin · · Score: 4, Insightful

      Yeah no shit. I'm awaiting the day that SCO claims that Osama himself has submitted patches to the kernel and that Alan Cox colaborated with Saddam Hussain in the mid 90's.

      They aren't first to try this though. There are a few large-ish companies (and one very large in particular - guess who!) that claim that Open Source in general and Linux in particular aids terrorists by providing them with a reliable and secure tool without intentionally placed backdoors (for law enforcement or otherwise).

      In other words, SCO is just a few years too late to try to claim that. Which brings up an interesting point: If MS accused Linux of something, can SCO do that now too? Or are they infringing on M$ accusation?

      --

      Jobs? Which jobs?
    10. Re:They must really be scared now. by barfomar · · Score: 5, Funny

      If I were a CEO of barely breathing tech company in the midst of a shakeout, I'd consider accumulating a few million shares of my company thru an off-shore broker when everybody is puking them out. Pick them up quietly, like gathering apples as they fall from the tree. Then, file some outgeous suit against some deep pocket, wait for the shares to multiply by 20-30 times, call my broker on payphone using a phone card purchased a gas station, and head for the islands. But, I'm not in that position....

    11. Re:They must really be scared now. by vladkrupin · · Score: 4, Insightful

      I personally think that this is SCO trying to get IBM to buy them out.

      Yes, it is also true that the sun is going to raise in the morning tomorrow. There are a few things that are plain obvious, true.

      On the other hand, they were doing a much better job trying to get bought out before today. At least they had something that resembled substantiated claims. Not anymore... I mean, it's almost a textbook example of how NOT to try to get bought out. Think of it:

      1. SCO isn't worth a billion bucks. Much less likely are they to be worth 3 billion. If IBM were to buy them, they would rather spend a few million bucks to buy them out rather than a billion dollars to settle, right? By upping the settlement three-fold SCO at best ticked off IBM a bit more, and have not contributed to their worth or their chances of being bought out one bit.

      2. Ticking off IBM for them is like a death warrant - if IBM was considering whether to sue them out of existence or be nice to them and buy them out, the chances of the latter happening are diminishing rapidly with every new claim against IBM SCO makes. SCO had to make sure that IBM takes them seriously. IBM understood that. SCO got IBM's attention. Now SCO has to sit back and pray that IBM will be nice to them. Instead they make more claims that makes IBM unhappy. Not very wise, if you ask me.

      3. Also, if this garbage EVER makes it to court, the judge has got to just laugh at the number - 3 billion! They could as well have claimed a trillion dollars in damages! It's like me suing you for a million bucks because your dog dug up my lawn!

      4. SCO tries to involve a dumb export restriction imposed by the government that never worked and has been abolished long ago because its effectiveness was zero, and pain for US companies was significant. I am not a lawyer, but it seems to me that whether or not IBM violated any export restrictions has nothing to do whatsoever with SCOs intellectual property. IBM has either misappropriated the IP and trade secrets or not - no government involved. If I buy a car from you and run a red light, I pay the ticket to the government; you have no right to try to take my car back!

      5. It's dumb to even mention something that just made its way into 2.5.43 kernel as something you own. I mean, you are suing for years of infringement, you are threatening corporate linux users who are still using 2.2 or 2.4, and presenting code that hasn't even made it into any stable kernels yet as evidence!

      6. And lastly, they just upped the number of claims of ownership on things that they clearly do not own. I thought their previous similar claims damaged their cridibility bad enough not to try that again. Looks like they haven't learned the lesson...

      At times I wonder, if they just figured they have a snowball's chance in hell to be bought out by IBM and just decided to make a really cool fun show for all of us to see...

      --

      Jobs? Which jobs?
  2. At least we know now what they're "smoking" by edgrale · · Score: 5, Funny


    "There are two major products that come from Berkeley : LSD and UNIX. We don't believe this to be a coincidence." -- Jeremy S. Anderson

    Soon SCO will claim ownership for LSD too ;)

    --
    09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
    1. Re:At least we know now what they're "smoking" by flacco · · Score: 4, Funny
      Soon SCO will claim ownership for LSD too ;)

      If they've already been experimenting with this technology, that would explain A LOT.

      --
      pr0n - keeping monitor glass spotless since 1981.
    2. Re:At least we know now what they're "smoking" by ae · · Score: 5, Insightful
      And LSD was developped in Switzerland, I think.

      Yes, LSD was synthesized by Dr Albert Hofmann in 1943, and he discovered its mind-altering properties while riding his bicycle on the way home. This is a quote from his laboratory notes:

      I suddenly became strangely inebriated. The external world became changed as in a dream. Objects appeared to gain inrelief; they assumed unusual dimensions; and colors became more glowing. Even self-perception and the sense of time were changed. When the eyes were closed, colored pictures flashed past in a quickly changing kaleidoscope. After a few hours, the not unpleasant inebriation, which had been experienced whilst I was fully conscious, disappeared. what had caused this condition?

      More information can be found here and here.

      --
      Blog Ho
  3. IBM's view by Anonymous Coward · · Score: 5, Funny

    Three times nothing is still nothing.

    1. Re:IBM's view by TopShelf · · Score: 5, Funny

      And pretty soon this will venture into the realm of imaginary numbers.

      "Today IBM successfully convinced the judge to amend the claim to $3 i Billion, to reflect the imaginary validity of SCO's case"

      --
      Stop by my site where I write about ERP systems & more
  4. Open Letter to CmdrTaco by Anonymous Coward · · Score: 4, Funny
    Mr. Taco;

    On behalf of the /. crowd, I am formally requesting that the Caldera/SCO widget be changed to a steaming pile of poo.

    We feel that this is more appropriate.

    Sincerely, /.

    1. Re:Open Letter to CmdrTaco by Anonymous Coward · · Score: 5, Funny

      Actually, I believe the "It's Funny, laugh" logo of the Monty Python foot suitably amended with at least one smoking bullet hole through it, would be far more approriate for SCO v's The World stories.

    2. Re:Open Letter to CmdrTaco by bubbha · · Score: 5, Funny

      How about Dr. Evil with his pinky raised to the corner of his mouth saying "Three Billion Dollars!"

      --
      I want to be alone with the sandwich
  5. SMP? RCU? by Surak · · Score: 4, Interesting

    What?

    Since when did IBM have anything to do with SMP in the kernel?

    And RCU is clearly a technology that Sequent designed for DYNIX/ptx. Sequent, as the link to RCU states, is now owned by IBM, so I suppose they'd have clear rights to this, no problem. RCU is also notoriously absent from SCO's product, so how they can claim ownership of the technology is beyond me.

    I'm starting to think that the folks at SCO are on SERIOUS crack and they AREN'T SHARING. There's reason enough to hate them right there, forget all this Linux stuff. ;)

  6. IBM should countersue... by joeszilagyi · · Score: 5, Funny

    ...on grounds of comedy. This is starting to turn into an old Looney Tunes cartoon, where the SCO Coyote throws everything but the Acme kitchen sink at the IBM Roadrunner. Meep meep!

    --
    Dude, where's my packet?
    1. Re:IBM should countersue... by testy · · Score: 5, Funny

      I disagree. IBM is more like the oncoming train that Wile E. McBridey sees in the tunnel, thinking it's the light at the end.

  7. Slashdot - by the_Bionic_lemming · · Score: 5, Funny

    Hmm - five - six more articles maybe, and SCO will become the most posted/hated OS on Slashdot?

    I wonder how Bill Gates will take losing the "Number One" spot here at /. ;)

    --
    _ _ _ Go for the eyes Boo! GO FOR THE EYES!
  8. .. and verification: by peatbakke · · Score: 5, Interesting

    Wish I had googled before posting, but here's the dirt:

    http://www.linux.org.uk/SMP/title.html .. maybe IBM refined the process later, but it looks like SMP is in the Linux kernel as a *direct* result of Caldera's actions.

  9. The development kernel? by realnowhereman · · Score: 4, Insightful

    Further - how can SCO be upping there damages if the infringing code is in the development kernel; that has nowhere near as wide a circulation as the stable tree. In fact (if they were right -- although obviously they're not) surely their duty of care would be to say which parts of the development kernel are infringing so that they can be removed before they get distributed to the four winds?

    Of course, I know who I'd like to distribute to the four winds.

    --
    Carpe Daemon
  10. Re:SCO is... by AKnightCowboy · · Score: 4, Insightful
    SCO is DYING to be bought out. They're grasping at whatever straws they can find, thinking that IBM the vampire slayer will finally drive a buyout stake through their black heart.

    I think IBM has found it's much more satisfying to slowly drain the blood from their prey over the course of many years of heated battle in a courtroom rather than go for a quick kill. Lawyers are very expensive and this will be a war of attrition. IBM will win simply because they will have the resources to stick this out for the long haul. They should be in NO hurry to settle this. Every day they delay is another couple hundred thousand dollars drained out of SCO's war chest by expensive lawyers.

  11. SCO does not own RCU! by xyote · · Score: 5, Informative

    Even IBM doesn't own it. It's in the public domain. Because it was invented by IBM 3 times (hey, it's a big company). Once in the mid 80's in VM/XA Rel 2 (patent 4,809,168 now expired), once at Sequent which was acquired by IBM and where RCU was coined, and once as part of the K42 project at IBM research.

    1. Re:SCO does not own RCU! by _|()|\| · · Score: 5, Informative
      The code that found its way into Linux is "based on original DYNIX/ptx code (released by IBM under GPL)." SCO's position is that everything in DYNIX/ptx, including RCU, is derivative of System V.

      Most of us assumed that SCO's chest thumping about copyright infringement referred to literal copying of System V or Monterey code. Now, it seems, it is based on the more tenuous theory that any part of a System V-based O/S is derivative.

  12. Re:SMP? RCU? by dschuetz · · Score: 4, Informative

    Since when did IBM have anything to do with SMP in the kernel?

    I think they're complaining that SMP was a restricted technology, so by helping to add SMP to the Linux kernel, and making it freely available, IBM violated US export laws. By violating those laws, IBM is therefore in violation of the SCO / IBM license agreement (not sure how that connection was made), and therefore, all rights assigned to IBM are void, blah, blah, blah, blah.

    They're asking a judge for an injunction now? Good. The sooner the judicial system gets a chance to take a formal look at this, the better.

  13. Highlights and changes in tactics by Badgerman · · Score: 5, Insightful

    These elements of the article stood out to me as indicating changes in tactics or tactics that they're planning to use:

    The amended suit also asserts that SCO holds copyrights to Unix, a point that could be key in future Linux and Unix litigation. Novell, which owned Unix intellectual property before selling it to SCO's predecessor, initially disputed SCO's ownership, but later relented.

    IANAL - I wonder why they've inserted this now. Did they forget? Is this just clarification? Are they hoping to get some mindshare here? It's weirder since the suit makes no claims of copyright violation . . .

    "As IBM executives know, a significant flaw of Linux is the inability and/or unwillingness of the Linux process manager, Linus Torvalds, to identify the intellectual property origins of contributed source code that comes in from those many different software developers. If source code is code copied from protected Unix code, there is no way for Linus Torvalds to identify that fact," the suit said. "As a result, a very significant amount of Unix protected code is currently found in Linux 2.4.x and Linux 2.5.x releases in violation of SCO's contractual rights and copyrights."

    I'm concerned this is getting personal (well, moreso). It casts doubt on Linus' competency and/or ethics, thus casting doubts on Linux, and I think may be a veiled threat towards Torvalds and suggest that in the future they may, as has been hinted, take action against him individually.

    Redesigning Linux for use by demanding business customers "is not technologically feasible or even possible at the enterprise level without (a) a high degree of design coordination, (b) access to expensive and sophisticated design and testing equipment; (c) access to Unix code and development methods; (d) Unix architectural experience; and (e) a very significant financial investment," the amended suit says.

    They either don't get how OS works or don't want to. Despite the changes, it pretty much the same thing - "Linux couldn't have gotten where it is without stealing. Which, by the way, is IBM and Linus' fault."

    The suit also adds illegal export issues stemming from the worldwide availability of open-source software. SCO claims IBM has breached its contract by making multiprocessor operating system technology available "for free distribution to anyone in the world," including residents of Cuba, Iran, Syria, North Korea and Libya, countries to which the United States controls exports. The open-source technology IBM released "can be used for encryption, scientific research and weapons research," the suit said.

    The only way I can sum this up is "If you use Linux, the terrorists have already won." This addition is rather odd, as if they are so worried, why wasn't this in the original suit? It smacks of exploiting the fear of terrorism and rogue nations for their own ends, and to me hints that their next strategy could be to focus on the idea that "Linx is unethical."

    Overall? I expect it to get more personal and more nasty on the part of SCO. I expect them to target Linus more, and possibly other developers or groups.

    --
    "The Sage treasures Unity and measures all things by it" - Lao Tzu
  14. Re:Revealed! Whole programs copied in Linux!! by cperciva · · Score: 4, Funny

    No. While a zero length file might be a functioning /bin/true, that isn't how it is implemented in SCO.

    At risk of provoking another lawsuit:


    # @(#) true.sh 1.4 88/11/11
    #
    #
    # UNIX is a registered trademark of AT&T
    # Portions Copyright 1976-1989 AT&T
    # Portions Copyright 1980-1989 Microsoft Corporation
    # Portions Copyright 1983-1989 The Santa Cruz Operation, Inc
    # All Rights Reserved

    # Copyright (c) 1984 AT&T
    # All Rights Reserved

    # THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF AT&T
    # The copyright notice above does not evidence any
    # actual or intended publication of such source code.

  15. IBM to SCO by earthforce_1 · · Score: 4, Funny


    I see your 3 billion and raise you two more. Show your cards...

    --
    My rights don't need management.
  16. Re:I've been away, so maybe this has been suggeste by KeoghX · · Score: 5, Funny

    FUD champagne? Is that the kind with scary bubbles?

  17. Godwin's law v2 by BenjyD · · Score: 4, Funny

    ... available "for free distribution to anyone in the world," including residents of Cuba, Iran, Syria, North Korea and Libya, countries to which the United States controls exports. The open-source technology IBM released "can be used for encryption, scientific research and weapons research," the suit said.

    So IBM is helping terrorists and rogue states now? I think we need an addition to Godwin's Law - "As a dispute goes on, the probability of one side claiming the other is helping terrorists approaches one"

    1. Re:Godwin's law v2 by Waab · · Score: 4, Funny

      There's no need to make an addition to Godwin's Law itself. From now on, we'll just have Godwin's Law and the Ashcroft Corollary.

  18. Actually, $50 Billion (story inside) by akiaki007 · · Score: 4, Informative

    Story from Bloomberg...

    BN 06/16 SCO Cancels IBM Contract, Seeks $50 Billion in Suit (Update4)

    SCO Cancels IBM Contract, Seeks $50 Billion in Suit (Update4)

    (Adds additional IBM comment in fourth paragraph.)

    June 16 (Bloomberg) --- SCO Group Inc. canceled International
    Business Machines Corp.'s contract for the AIX Unix operating
    system and revised a lawsuit against IBM to seek as much as $50
    billion.
    The amended complaint also seeks an order forbidding the
    sale of IBM's AIX operating system, SCO Chief Executive Darl
    McBride said. SCO, which licenses Unix to thousands of companies,
    sued IBM in March claiming it transferred Unix code into the
    related Linux operating system in breach of IBM's contract. IBM,
    the world's second-largest software maker, denies the claims.
    ``The meter is now ticking with respect to AIX and will be
    ticking until we get conclusion to this,'' McBride said in an
    interview. SCO is seeking from IBM ``any amount they get from the
    AIX or related business lines'' while the case is pending, an
    amount he said could run as high as $50 billion.
    IBM's AIX license is irrevocable and there is nothing in
    today's action that changes that, IBM spokeswoman Trink Guarino
    said. IBM will continue to ship AIX and develop products, the
    company said in a statement.
    SCO shares fell 28 cents, or 2.5 percent, to $10.93 at 4
    p.m. New York time in Nasdaq Stock Market trading after earlier
    dropping 14 percent to $9.60. Shares of IBM, the world's largest
    computer maker, rose $1.75 to $84.50 in New York Stock Exchange
    Composite trading. They've gained 9 percent this year.

    Impede Marketing

    SCO's lawsuit might hamper IBM and dozens of other
    companies' marketing of Linux, which Morgan Stanley and other
    companies use to cut costs, analysts said. Today's move escalates
    SCO's demands by expanding a previous demand of $1 billion in
    damages and seeking an injunction against AIX, which SoundView
    analyst John Jones said generated $2.8 billion in sales in 2002.
    ``For a fraction of that, IBM can buy SCO outright,'' said
    Carl Hoagland, an analyst with State Street Corp., referring to
    the demand for as much as $50 billion. ``Why bother to play these
    games?'' State Street is IBM's largest shareholder.
    Lindon, Utah-based SCO, worth about $134 million based on
    today's closing stock price, bought Novell Inc.'s licensing
    rights to Unix for $145 million in 1995. Novell, whose software
    is used to manage computer networks, last month challenged SCO's
    claims, saying Novell retains ownership of the Unix patents and
    copyrights. SCO maintains it has legal entitlement to them.
    SCO's suit was filed by attorney David Boies of Boies,
    Schiller & Flexner LLP, who represented the U.S. Justice
    Department in its antitrust lawsuit against Microsoft Corp. and
    Vice President Al Gore in his dispute over the 2000 presidential
    election results. Both Boies' firm and IBM are based in Armonk,
    New York.
    Linux, developed by Finnish developer Linus Torvalds, is
    maintained and updated by a corps of volunteer programmers who
    make it available for free over the Internet. Companies such as
    IBM, Oracle Corp. and Red Hat Inc. make money from Linux by
    selling computers, software and services related to the operating
    system.
    Unix was first developed in the late 1960s by AT&T Corp. Sun
    Microsystems Inc., Hewlett-Packard Co., IBM and other companies
    over the years derived their own operating systems based on Unix.
    Linux is one of the most recent Unix offshoots to emerge.
    Microsoft Corp. is the world's biggest software maker.

    --Jonathan Berr in the Princeton newsroom (1) (609) 750-4516 or
    jberr@Bloomberg.net. and Dan Goodin in San Francisco, (1) (415)
    743-3548 or dgoodin@bloomberg.net. Editor: Todd.

    --
    "Time is long and life is short, so begin to live while you still can." -EV
  19. Re:Only 3 billion? by Anonymous Coward · · Score: 5, Funny

    Why ask for 3 billion when we can ask for 3 _million_?

    *raises pinky finger to corner of mouth*

  20. Re:SMP? RCU? by jone1941 · · Score: 4, Funny

    It's like playing the Kevin Bacon game! Can you claim IBM broke your license agreement in less than 7 hops? Yes? Well then you've got a case. Sad. It's just sad.

    --
    Fear trumps hope and ignorance trumps both
  21. Something to consider... by Sheetrock · · Score: 5, Insightful
    Not only that, but there is also the cash infusion via the (re?)licensing of Unix from SCO to consider. I don't think it's an unfair suppository to make at all that Microsoft is viewing this as a high-risk low-cost gamble on SCO winning this fight.

    Kind of wierd when you think that Caldera (now SCO) acquired DR-DOS to do legal battle with Microsoft only two years ago, but I suppose that just illustrates the shifting loyalties on the intellectual property battlefield. IBM is good and all, but one wonders how long they'd back Linux if a better opportunity comes along.

    --

    Try not. Do or do not, there is no try.
    -- Dr. Spock, stardate 2822-3.




    1. Re:Something to consider... by tmhsiao · · Score: 5, Funny

      I don't think it's an unfair suppository to make at all that Microsoft is viewing this as a high-risk low-cost gamble on SCO winning this fight.

      I hate those unfair suppositories, especially from Microsoft.

      I always knew Bill Gates was trying to shove something up my bunghole.

      --
      "My God...It's full of ads!" -Fry, about the Internet, Futurama
    2. Re: Something to consider... by Black+Parrot · · Score: 4, Interesting


      > I don't think it's an unfair suppository to make at all that Microsoft is viewing this as a high-risk low-cost gamble on SCO winning this fight.

      It's not a gamble; it's a kamikazi attack. SCOX was almost worthless and their product had no future. Why let it fade away when you can turn it into a flaming bomb amid the enemy fleet?

      Notice that Microsoft wins whether SCO wins or not. The only interesting question is whether SCO's executives are dupes or willing conspirators.

      --
      Sheesh, evil *and* a jerk. -- Jade
  22. Re:SCO is... by Crockerboy · · Score: 5, Insightful

    IBM will win simply because they will have the resources to stick this out for the long haul.

    It's sad really that this is the reason they will will, not because they are in the right or anything...

  23. Re:As exciting as it is... by Sven+Tuerpe · · Score: 4, Insightful
    When is SCO going to get crushed like a lone sidewalk snail?

    Why hope to see them crushed? They provide a pretty useful service to the public: demonstrating that the concept of intellectual property leads to poor results if applied in the manner shown by SCO. Intellectual property is a nice idea if used e.g. by an artist to protect her works from unauthorized altering, or if it helps an inventor to make a living. It is not if separated from the actual, individual creators of something; it is not if used to revoke transactions after the fact; it is not if applied to prevent people from tinkering with things they did buy. Now we have a showcase. Thank you, SCO!

    --
    http://erichsieht.wordpress.com/category/english/
  24. Re:SMP? RCU? by Surak · · Score: 5, Interesting

    Um, IBM didn't make Linux freely available. Linus Torvalds did. They contributed to the code, but they didn't contribute the SMP code. THey contributed the RCU thing which helps with SMP, but the SMP code itself was already in there, and hence, if anyone is liable for SMP code being in there it's Alan Cox -- and he's in the U.K. and can't be held liable for U.S. export laws.

    SCO is high. That's the only explanation here. ;)

  25. Export Regulations by vandan · · Score: 4, Insightful

    I've always thought that the Export Regulation laws were screwed.
    Why would Iran, Syria, or whoever want to build a supercomputer to simulate a nuclear explosion, when they only have to ask the fucking yankees nicely and they will gladly provide them with the real thing "oh sure it killed millions of people & animals and poisened hundres of millions for millions of years to come, but think of how many american lives it saved".

    Seriosly, nuclear explosions have been studied to death (pun intended). Anyone serious about taking a shot at the US (I'm sure there are some out there) only need pay a laughably insignificant amount of money either on the black market or to the arms manufacturers who don't give a frig about what the Pentagon would like.

    Preventing SMP and supercomputer technology (and the fucking web browser I'm using, for fuck's sake) from entering [insert anti-american country here] is just demonstrating american arrogance. I'm sure it is done in the same spirit as all the bans on medical equipment entering Iraq. Can't have the fuckers healing themselves! The yankees aren't too keen on keeping their karma high, are they?

  26. the weirdest claim by Artifex · · Score: 4, Insightful

    SCO is asserting that IBM is violating export controls, but how that has anything to do with SCO is anyone's guess, unless of course SCO is claiming unfair competition in the giving-tech-to-hostile-countries-market.

    Seriously, only the U.S. government can really have much of a case against them for that, if in fact they are in violation.

    This is like one of my first graders, back when I tutored, coming up to me and complaining that some other kid was hogging the smelly markers (he had 1), oh and also, know what know what know what know what? He threw a rock at the doggy they saw on the way home yesterday, too!

    In other words, a finger-pointing smear campaign, because the original complaint is meritless.
    At least little kids are guileless enough to blush and admit it, when you call them on it.

    --
    Get off my launchpad!
  27. Sun sponsoring SCO? Possible proof! by ultrabot · · Score: 5, Insightful

    I'm reposting this, since the previous posting was to an article that was pretty dead already .

    From McBride interview at ZDNet:

    How did Microsoft's agreement to pay you for Unix rights happen?

    Darl: In the Microsoft case, they saw an opportunity. We originally approached them and said we're on a new licensing path; we have this intellectual property that we've started approaching vendors about. IBM is one we approached; Microsoft was another. We had about four big vendors in the last quarter that we talked with. With two of them, we signed deals. The other we're still talking with, and IBM we reached an impasse.

    To me it feels like they are still talking with HP, and Sun decided to pay up to take a stab at linux (in the back, I might as well say). Or is there any other interpretation? Was anyone surprised at how quick Sun was to advertise that they are in the clear?

    Also, SCO has said that Sun is the only company that is clear of all the violations. Even M$ is less clear.

    I hope someone brings this up in an interview with Scott, so he can explicitly deny this if it is untrue.

    --
    Save your wrists today - switch to Dvorak
  28. Re:Revealed! Whole programs copied in Linux!! by countach · · Score: 5, Funny

    Well, duh. The plagarist removed the copyright notice. They're not THAT silly!

    But shame on you for revealing all of SCO's intellectual property! Don't you realise what this will do to their stock price? You've got a trade secret law suit on the way buddy.

  29. SCO claims RCU is derivative of SysV by _|()|\| · · Score: 5, Interesting
    RCU is also notoriously absent from SCO's product, so how they can claim ownership of the technology is beyond me.

    The latest twist in the lawsuit is revealed in a recent CNET interview of Darl McBride: "The System 5 source code, that is really the area that gives us incredible rights, because it includes the control rights on the derivative works that branch off from that trunk. " It is SCO's position that JFS and RCU are derivative of System V.

    Opponents of the GNU General Public License perpetuate the misconception that it is somehow viral. In fact, it is copyright law itself that is viral. Quoting from IP in a Nutshell:

    A copyright owner has the right to exclude all others from creating works based on his own. ... The statutory definition of a "derivative work" is extremeley comprehensive, including such things as translations, arrangements, dramatizations, fictionalizations, films, recordings, abridgments, condensations, "or any other form in which a work may be recast, transformed, or adapted."
    If carried to its conclusion, this suit could be the textbook on derivative works with regard to software.
    1. Re:SCO claims RCU is derivative of SysV by Matrix272 · · Score: 4, Funny

      But that doesn't apply to parodies... so maybe IBM just released a "parody" of System V, eh?

      You can only fight insanity with insanity.

      --
      "It's better to have a gun and not need it than need a gun and not have it." ~ Christian Slater, True Romance
    2. Re:SCO claims RCU is derivative of SysV by Nutcase · · Score: 4, Interesting

      So they are saying the SysV license gives them rights to all derivitive works.. sort of a proprietary version of the GPL's "viral" nature.

      So if they win, the GPL also gains strength via precedent, but free software loses credibility as a development model.

      And if they lose, the GPL /loses/ credibility as a solid license, and it's enforcability comes into question.

      That's sneaky as hell. Whoever thought this up spent a long time covering their bases. For the first time, I am somewhat worried.

    3. Re:SCO claims RCU is derivative of SysV by Sancho · · Score: 5, Insightful

      The license of the GPL is different from the "viral" copyright law. I would suggest that it would not lose any credibility as a solid license or in enforcability. The GPL doesn't claim that violations result in all derivative works transferring back to the original copyright holder, just that derivative works must also be GPL. That should be a lot easier to get past a judge than SCO's claims....we hope, at least.

  30. Re:SMP? RCU? by cowmix · · Score: 4, Interesting

    "More to the point,
    as noted in the OSI position paper on the lawsuit
    (about half way down - search for SMP and you will eventually find the
    correct segment), Linux had working SMP before UNIX did, so this is a
    null claim."


    Arg.. ESR has that wrong. SMP was
    not working on Linux first.. Both the UnixWare and SCO UNIX banches had
    SMP working before Linux.

  31. Re:I don't un'erstan', padre... by akiaki007 · · Score: 4, Interesting

    What does SCO hope to gain?
    1 Billion Dollars. Which would six-tuple their revenue from the last year. That's a lot.

    Do they really think they have a chance against IBM's lawyers?
    Not a chance. Not especially since it's not just IBM, but the Linux community acting out against them. Just yesterday a programmer from Germany sent SCO a letter asking them to stop using OpenUnix and to provide him of all information as to who is running it, because it contains his copyrighted Linux kernel code and OpenUnix violates GPL (not part of it). I 'm sorry, I can't remember his name

    Do they think they really have a case? Is this just some blatant attention-getting tactic?
    I don't think so, and many don't. Attention getting? I think so. Their stocks were 2$ in Feb, and now are at 10.50 (as of 17:05 yesterday), and will open .40 cents lower than yesterday's close. That is a huge gain. Lots of attention. Also, their VP is selling 10,000 shares on open this morning (cash in obviously). He probably thinks they've reached their high point and have no where to go but down. The case currently stands at 50$ billion, and that is a LOT of attention. The company itslef is only worth a couple hundred million dollars, and IBM could easily just squash them with a hostile bid and buy out all their stock. Which I'm sure SCO execs would love, because the shares are incredibly high compared to Feb '03. Will IBM? Why would they? They get nothing out of the deal except a mouse. They'll play SCO's cards and see where it takes them. Perhaps in the end IBM will buy SCO (then MSFT will be paying IBM for the Unix licence ;))

    --
    "Time is long and life is short, so begin to live while you still can." -EV
  32. Future think by Ignorant+Aardvark · · Score: 4, Funny

    Translation of the next obfuscated memo to come out of IBM:

    No, seriously, you need to fuck off now. It's not funny anymore.

  33. Re:Hmm... by LizardKing · · Score: 5, Interesting

    SCO claims that the SMP jumped from 4 processors to 64, something that the linux community could not do on their own, mostly because none of us could afford a 64 proc machine

    I remember someone porting SMP Linux to a Sun ES10000 machine and posting the dmesg output to the kernel mailing list. That particular ES10000 sported 64 processors if memory serves, and this feat was accomplished long before IBM became a big Linux player.

    From what I remember of Linux SMP capabilities circa 2.2.x, it could scale to a large number of processors, but PC's mobos were only available with a maximum of four processor slots. I'm pretty sure that's where the "only four processors" thing comes from.

    Chris

  34. Re:SMP? RCU? by Waffle+Iron · · Score: 5, Funny
    I think they're complaining that SMP was a restricted technology, so by helping to add SMP to the Linux kernel, and making it freely available, IBM violated US export laws.

    Who else very recently made the Linux kernel freely available to any foreign party including terrorists, communists and all three vertices of the Axis of Evil?

    Hmmm?

    Could it be .... SCO!!!???

    Didn't they do the due dilligence to see if the capabilities that they were distributing were exportable under U.S. law? Looks like they didn't, and now OBL himself could very well be running Caldera Linux on the Beowulf cluster in his cave simulating thermonuclear explosions.

  35. Re:Timeline of SCO events? by iwaku · · Score: 4, Informative

    This might help: http://news.com.com/2104-1016_3-1017965.html

  36. Still running on the stock scam theory by Jerf · · Score: 4, Interesting

    I'm still running on the stock scam theory. It explains the escalating shrillness of SCO (must stay in the news to affect the stock price) better then anything else.

    I'm not buying the Microsoft support conspiracy theory because whatever else you may think, you have to concede that Microsoft is a smart company and if they were going to indirectly support SCO in this, they would not leave an blatently obvious money trail to SCO. I think they licensed SCO's IP to just make them go away. Microsoft may have a huge legal team but odds are they are not sitting in Redmond twiddling their fingers; all else being equal even a company as large as Microsoft would probably prefer not to add another lawsuit to its plate.

    Without the Microsoft support (IMHO), the "trying to discredit Linux" isn't the motivation, it's just a side-effect of their need to continually ramp up the volume.

    If I'm right then we'll know in a bit; SCO can't maintain this volume much longer. I predict that in the next couple of weeks, SCO will unexpectedly drop the suit... and quite possible fold entirely.

  37. Huh? by Catiline · · Score: 5, Insightful
    "As IBM executives know, a significant flaw of Linux is the inability ... of the Linux process manager, Linus Torvalds, to identify the intellectual property origins of contributed source code.... If [contributed] source code is code copied from protected Unix code, there is no way for Linus Torvalds to identify that fact," the [filing] said.

    Is this a flaw of Linux, or just the simple fact that SCO is claiming that their closed source system is being infringed? 'Closed source' means the general public -- including the esteemed Mr. Torvalds -- are not privy to the original code. So exactly what method of verification did SCO have in mind for Linux developers to follow? Of course, we then have Linus' (less directed) retort:

    "It's not our side that isn't identifying the code. We'll work damn hard to identify everything they care to name," Torvalds said. "In fact, the source control system is out there in the public, and it identifies the source and the reason for patches."

    IOW, "we can't identify infringing code and remove it if you refuse to give us that information. Our process is out in the open and you are able to glean all the facts you may need ... what's your holdup?"

  38. SCO = next Enron by dh003i · · Score: 4, Insightful

    It is obvious that the executives of this company have no long-term business plan for SCO. This lawsuit is obviously entirely bogus -- see the OSI position paper on it, and if it had any value IMB would have settled or bought SCO.

    Rather than focusing on creating a sound business plan and actually making a good product which consumers want to buy -- something which SCO has failed to do as of yet -- they have chosen to throw baseless allegations around. It generates stock-market interest.

    They are obviously planning on doing some insider trading, selling out the investors when the stock is at it's peak, long before the inevitable crash.

    As for the allegation that Torvalds can't determine what code contributed is proprietary, no-one can within reasonable means. The best anyone can do is get those contributing to accept responsibility for the contributed code and sign a legal agreement stating that it is their own code. He, nor anyone else, cannot put out bulletins asking the world "is this anyone's proprietary code" before contributing something to the kernel. Many companies would lie and say it was, wasting his time and putting an undue burden on him. Furthermore, he'd have no way of verifying such claims.

    The best approach to writing software is exactly what Linus has advocated. Pay no attention to legal patent/copyright, and simply write code. When accepting code from other's, make them claim liability for it, and legally say that it is their own, or code they're allowed to contribute to the best of their knowledge. Trying to find out for sure if contributed code may or may not be copyrighted is an undue burden, and puts additional liability on developers.

    Btw, Linux is international. So is GNU software. This lawsuite, even if it's claims of misappropriation are true, will not necessarily force any changes in Linux or GNU/Linux. If any code is SCO's, however, for the convenience of those working in the US, it will rapidly be coded around. This is a non-issue no matter which way you look at it.

  39. Future lawsuit headlines by fireboy1919 · · Score: 5, Funny

    SCO upps damages to 6 billion - citing IBM's illegal use of 'international business machines' acroynm which they thought up first.

    Damages go up to 15 trillion when SCO discovers that gravity and other basic laws of the Universe which IBM has been using to build servers formed a basis for SCO's machines first.

    Finally, SCO ups damages to (quoting here) "forty bazillion-kabillion" for "having a successful business," which is what SCO was planning to do but couldn't because of IBM.

    It should be noted that this last figure was given just before the Executive board collectively passed out after coming down dangerously from a hallucenagic high caused by dry-erase markers, non-dairy creamer, pez, and possibly other office-related recreational drugs.

    --
    Mod me down and I will become more powerful than you can possibly imagine!
  40. Re:SMP? RCU? by Bootsy+Collins · · Score: 5, Insightful

    And RCU is clearly a technology that Sequent designed for DYNIX/ptx. Sequent, as the link to RCU states, is now owned by IBM, so I suppose they'd have clear rights to this, no problem. RCU is also notoriously absent from SCO's product, so how they can claim ownership of the technology is beyond me.

    OK, I could be completely wrong here. Lord knows trying to figure out what's in these people's minds is hard. But here's what I think is going on, and why they make such a claim. I preface this by saying that it was other posters here, in yesterday's SCO-related articles, that first made this point to me. First, check out this C|Net article, containing a brief interview with the CEO of SCO. In particular, note this quote:

    Where people get a little confused is when they think of SCO Unix as just the Unix that runs the cash register at McDonalds. We think of this as a tree. We have the tree trunk, with Unix System 5 running right down the middle of the trunk. That is our core ownership position on Unix.

    Off the tree trunk, you have a number of branches, and these are the various flavors of Unix. HP-UX, IBM's AIX, Sun Solaris, Fujitsu, NEC--there are a number of flavors out there. SCO has a couple of flavors, too, called OpenServer and UnixWare. But don't confuse the branches with the trunk. The System 5 source code, that is really the area that gives us incredible rights, because it includes the control rights on the derivative works that branch off from that trunk.

    I added the boldface to that last clause for emphasis.

    Similarly, Chris Sontag, SCO's Senior Vice President of the Operating Systems Division, said the following in this Byte magazine article:

    We believe that UNIX System V provided the basic building blocks for all subsequent computer operating systems, and that they all tend to be derived from UNIX System V (and therefore are claimed as SCO's intellectual property).

    The point is that I think they feel they have some sort of rights over the additional code and technologies that licensees add to the System V code they license from SCO in the process of creating their particular product. IBM bought Sequent, acquiring Sequent's RCU technology. IBM added that technology to AIX. Apparently, in SCO's mind, that gives SCO some degree of rights over that technology, because it's now part of AIX, and AIX is a derivative work of SCO's System V code, and SCO believes they have some amount of rights over all derivative works. And therefore, claims SCO, adding it to Linux violated SCO's rights.

    This seems like what they're saying. It also seems completely nuts -- unless IBM's license for SysV code for AIX gives the rights for technologies they come up with and add to AIX back to the owner of the System V codebase. I can't imagine that being true, though.

    Another read on this is that it looks even more than it did before like an attempt to re-try the Unix Systems Labs vs. BSD case.

  41. Re:Release the ninjas... by Mohammed+Al-Sahaf · · Score: 5, Funny
    There is no way penguins can write SMP code without our help. We will slaughter all the penquins and have them for dinner
    As SCO's new press minister, I can confirm this.

    IBM are a superpower of villains. They are superpower of Al Capone. These cowards have no morals - they have no shame about lying. We will slaughter them all .... most of them. The situation is excellent, they are going to try to sue us, and I believe their grave will be there. We will push those crooks, those mercenaries back into the swamp!

    Mohammed al-Sahaf (now SCO press spokesman)
    --
    Former Iraqi Information Minister Mohammed Saeed al-Sahaf
  42. Re:the weirdest claim -- SCO exported it too... by BadElf · · Score: 4, Insightful

    From the article: "...for free distribution to anyone in the world," including residents of Cuba, Iran, Syria, North Korea and Libya, countries to which the United States controls exports."

    The last I heard, Linux has been (and is) developed by folks from all over the world -- including the countries in question -- so how does "export" even come into play here?

    Using SCO's own twisted logic, wouldn't SCO itself be responsible for "exporting" banned code to these countries by making its distros available on their FTP servers?

  43. Re:SMP? RCU? by Surak · · Score: 4, Interesting

    Another read on this is that it looks even more than it did before like an attempt to re-try the Unix Systems Labs vs. BSD case.

    Yeah, and USL lost on that one. IBM's SysV license comes from AT&T, it did not originate from SCO. So IBM had the license with USL, and then later Novell, and then later SCO, and then later Caldera, and then later SCO.

    Okay. So if USL lost, then the precedence has already been set -- USL didn't have rights to derivative works as ruled by the courts, so neither does SCO, because SCO has the same rights USL had, presumably. The OSI position paper covers this.

    Yeah, so SCO even in your scenario, is STILL on crack and they STILL aren't sharing.

    Also, tinfoil hat mode, Look at Sontag's quote:

    We believe that UNIX System V provided the basic building blocks for all Subsequent Computer Operating systems, and that they all tend to be derived from UNIX System V (and therefore are claimed as SCO's intellectual property).

    Hmmmmm ....conspiracy? they changed their name to SCO Group to reflect their main source of revenue, which apparently is everyone who makes an operating system that comes after Unix. :)

  44. Inconceivable by Spazmania · · Score: 4, Funny

    Redesigning Linux for use by demanding business customers "is not technologically feasible or even possible at the enterprise level without (a) a high degree of design coordination, (b) access to expensive and sophisticated design and testing equipment; (c) access to Unix code and development methods; (d) Unix architectural experience; and (e) a very significant financial investment," the amended suit says.

    SCO: They built a better OS using so-called open source methods? Inconceivable!

    IBM: You keep using that word. I do not think it means what you think it means.

    --
    Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
  45. Waiting for IBM response by joncarwash · · Score: 5, Interesting

    I don't know about anyone else, but I am waiting for IBM's response to all of this in court. I hope that they don't seal up everything because I would like to see their defense (or offense? - hey, the best defense is a good offense, right?).

    So far, IBM has only made small comments basically shoving aside the entire situation, like their most recent:

    Since filing a lawsuit against IBM, SCO has made public statements and accusations about IBM's Unix license and about Linux in an apparent attempt to create fear uncertainty and doubt among IBM's customers and the open source community.
    IBM's Unix license is irrevocable, perpetual and fully paid up. It cannot be terminated. This matter will eventually be resolved in the normal legal process.
    IBM will continue to ship, support and develop AIX which represents years of IBM innovation, hundreds of millions of dollars of investment and many patents. As always, IBM will stand behind our products and our customers.

    I also remember at the beginning of this whole mess, IBM stated that they wanted this to go to court (specifically a jury trial if I remember correctly). I have no doubt that the IBM legal department has some very interesting material/arguments that they are ready to show everyone.

    Maybe SCO has been spewing with new "revelations" and "violations" but I am sure the very adept IBM legal department has been getting something ready that SCO won't stand a chance against.

    On slashdot (and many other places) people are really getting played by the SCO "FUD" meanwhile IBM doesn't seem to be playing anything up - and people seem to forget what company we are talking about here - the same IBM that has been around since forever and has fought their share of legal battles.

    We should have a little more confidence that good old Big Blue knows what they are doing here and not try to kill ourselves with the B$ flowing out of SCO.

    --
    A computer is a valuable tool, so use it and stop whining.
  46. Re:Hmm... by Angry+White+Guy · · Score: 4, Interesting

    It could scale, but not as effectively as Unix. That's where the RCU code comes into play. Without the RCU code, the bottlenecks barely show on 4-way systems, but begin compounding after that. From the RCU Article linked in the story: "Using RCU it is possible to provide some relief from acquiring dcache_lock. The main work of dentry cache is done in looking up existing dentries in the cache which is done by d_lookup routine. Using RCU (and lazy-lru algorithm), we could do lock-less lookup for dentries and bring down the contention for dcache_lock while running dbench considerably from 16.5% to 0.95% on an 8-way SMP box. Recent measurements by Anton showed > 20% improvement in dbench throughput for a 32-way PPC machine." So even though a standard SMP kernel pre-patch could do SMP, the (allegedly)Sco owned code made the kernel 'Enterprise Ready'

    --
    You think that I'm crazy, you should see this guy!
  47. SCO is a Microsoft Patsy by Ranger · · Score: 4, Interesting

    The more I read about this lawsuit the more I'm convinced that SCO is a Microsoft Patsyâ. It doesn't matter if SCO loses as long as it damages the Linux community in the eyes of corporate users. And Microsoft Patsy â will drag this out as long as it takes. It's a lose-lose situation for SCO, Linux, and IBM and a win-win situation for Microsoft.

    --
    "You'll get nothing, and you'll like it!"
    1. Re:SCO is a Microsoft Patsy by walterbyrd · · Score: 4, Insightful

      I know that on /. it's always fashionable to bash msft. but the truth is that sunw has more to win from this than msft.

      - sun hope to convert aix users to solaris.

      - linux and freebsd hurt sun more than msft.

  48. Re:SMP? RCU? by ajs · · Score: 4, Interesting

    Hmmm.. that's a fine point, and I'm not sure I agree with you.

    First off, it depends on your definitions. Having a port to a platform that isn't part of the core project, IMHO does not count (especially since that port is not techinically what SCO is claiming IBM took).

    UnixWare, AFAIK, did not have a core SMP capability prior to Linux. SCO Unix on the other hand may have, I'm not sure. Those are, of course, very different products, and again I think SCO is claiming that the Unix license that was sold to IBM *prior* to SCO's acquisition of the rights are the point of "IP loss", so claiming that they had it first in SCO would not help.

    I would love to hear people who used to work for Novell weigh in on the timeline. I know that Linux had SMP on certain limited motherboards VERY early on and as early as v0.27, 05 may 1998, the new motherboards were being added to the already growing list of Linux SMP platforms....

  49. Re:/. pathetic response by lovebyte · · Score: 4, Informative

    You are right about /. pathetic response. I think the most interesting point is this:

    * Is including controlled technologies in Linux the equivalent of violating US export laws? That could have implications far beyond SCO's suit.

    It could, but mostly for US companies and developers. Let's not forget that GNU/Linux is an international effort.

    --

    I'll do it for cheesy poofs.

  50. linux is only the start by in1t · · Score: 4, Interesting

    According to an article on byte.com, Linux is only the start. BSD,Windows,MAC could potentially be targets as wells. SCO appears to beleive that all operating systems are derived in some way from Unix System V technology. I think they are hoping if they stink loud enough someone buy them out. (Byte article is here

  51. IBM and Linux SMP by CrudPuppy · · Score: 5, Informative


    I hate to break it to SCO, but Linux had SMP support LOOOOOONG before IBM got into the open source game. Idiots.

    I hope SCO execs have to sell their kidneys to pay for the lawsuit filed by IBM when courts figure out how unsubstantiated these claims truly are!

    --
    A year spent in artificial intelligence is enough to make one believe in God.
    1. Re:IBM and Linux SMP by LO0G · · Score: 5, Informative

      The issue isn't whether or not Linux had SMP support.

      The issue is whether or not the source code in Linux was written by SCO or not.

      Similarly, the comment in the topic about RCU being invented by Sequent is irrelevant. The issue is if the code that implements RCU in the Linux kernel was written by SCO.

      If the code was written by SCO, then they have a case. If it wasn't, they don't.

      Remember - SCO's not claiming patent infringement, they're claiming copyright violation. Their claim is that the Linux kernel contains code that was written by SCO and shared with IBM under SCO's license to IBM. They claim that IBM then turned around and inserted that code into the Linux kernel that they distributed, thus violating SCO's copyright.

      Whether or not the concepts that are embodied in that code were original to SCO is utterly irrelevant to SCOs case. The ONLY issue is whether or not SCO's code appears in the Linux kernel.

    2. Re:IBM and Linux SMP by tyllwin · · Score: 5, Insightful

      No, let's be clear: IMHO, the issue -- at least in this lawsuit -- is *not* "whether or not SCO's code appears in the Linux kernel." The issue is whether or not they can provce that *IBM* put SCO code into the Linux kernel. If SCO code got into the Linux kernel some other way, they have no case against IBM, at least.

    3. Re:IBM and Linux SMP by surprise_audit · · Score: 4, Interesting
      The issue isn't whether or not Linux had SMP support.

      The issue is whether or not the source code in Linux was written by SCO or not.

      To be strictly accurate, this case is about whether IBM was responsible for SCO's alleged SMP code being ported to Linux.

      If the Linux Kernel commits show that: 1) Linux got SMP before IBM was involved; and/or 2) that the developer(s) who submitted the SMP code had no connection with IBM, then SCO's immediate case against IBM falls apart.

      I mean, it's possible that SCO's code could reach Linux some other way, not just via IBM, right? I'm not saying it did, just that it's possible. If it can be proved that Linux' SMP code is in no way related to IBM, then SCO has just dug their grave a little deeper - at the very least, IBM can counter-sue for libel, slander (probably), illegal restraint of trade and attempted extortion. Add to that 100's of IBM's patents SCO are probably violating, I'd say they're most definitely fucked

  52. Letter to IBM by umrgregg · · Score: 5, Funny

    Dear Mr. Palmisano:

    I have become aware of a litigious situation between your company and that of Darl McBride (SCO). In your pending defense against their lawsuit(s) I would like to recommend to you that I, NMG be your sole defense attorney. I am not on your legal defense team, nor am I actually a lawyer. I am merely a reader of Slashdot. SCOâ(TM)s claimâ(TM)s of damages are so ludicrous, I believe that even a troop of Screaming Monkeyâ(TM)s could provide you proper defense. Unfortunately for you, the Screaming Monkeyâ(TM)s were already hired out for the year by the Federal Trade Commission. Therefore, I extend an offer of my services for your legal defense in return for a pack of smokes, a ThinkPad and a chance to punch SCO in the kisser. This union will save you a bundle of money in defense feeâ(TM)s and will save your legal resources for your pending investigation with the horde of Screaming Monkeyâ(TM)s. Thank you for your time.

    Sincerely,

    --
    NMG
  53. Re:SMP? RCU? by shoppa · · Score: 4, Insightful
    Alan Cox -- and he's in the U.K. and can't be held liable for U.S. export laws

    While that's pure common sense, we're dealing with legalities and attorney generals who pride themselves on applying our laws to those devious foreigners. Alan Cox may be paranoid about coming to the US but he has good reasons.

  54. Re:SMP? RCU? by Anonymous Coward · · Score: 5, Interesting

    Didn't Caldera give Alan Cox an SMP system?

  55. Sun Microsystems joins the debate by smoondog · · Score: 5, Interesting

    According to Infoworld, Sun has joined the debate by taking advantage of the uncertainty over IBM. They have taken out advertisements questioning the use of AIX over Solaris.

    -Sean

  56. Re:I wouldn't mind... by Ignominious+Cow+Herd · · Score: 4, Funny

    "To do is to be" - Socrates.

    "To be is to do" - Plato.

    "Do be do be do" - Sinatra.


    "Please pass the doobie" - Darl McBride.

    --
    Lump lingered last in line for brains, and the ones she got were sorta rotten and insane.
  57. Re:SMP? RCU? by Royster · · Score: 4, Informative

    Your understanding of the USL/BSD case is faulty. While the court did find that BSD included a small amount of code from AT&T, they also found that AT&T took much more than that from BSD.

    Your understanding of derivative works is similarly faulty. While it's true that the issue of what is a derivative work in software has never been litigated, it is not true that the owner of the original work owns the copyright to the derivative work. When a company, like IBM, buys the right to make derivative works, they own the copyright on the derivative work. Disney bought the rights to make films from A.A. Milne's Winnie the Pooh. The Milne heirs do not own the rights to those films, Disney does.

    --
    I have discovered a truly marvelous sig, unfortunately the sig limit is too small to contain i
  58. The patriotic fallback by theolein · · Score: 4, Insightful

    The claim that IBM is aiding terrorism is something so cliched in America it's almost not even funny anymore. This is something so typically used as a last ditch defense when everything else fails that most people should be able to see it with ease. SCO's claims have varied from copyright infringment until proven otherwise, through contract breach by releasing SCO code until IBM called that bluff as well, up until now when SCO goes for the patriotic kneejerk reaction hoping to rally Americans to the cause.

    Incidentally, they're also claming RCU is in breach of contract. The RCU might very well be in breach of contract in that Sequent added code to Linux although that code was developed under the Unix licence from SCO. Sequent was bought by IBM and that makes IBM guilty although I'm not sure that SCO can claim ownership of anything that Sequent developed unless there was an agreement between them.

    Which would in fact leave only the patriotic fallback, and I'm pretty sure that that one is not going to hold up in court.

    So, in other words, you're fucked Darl.

  59. How do you know what they're claiming? by dark-nl · · Score: 5, Informative

    SCO has been all over the place about what they're claiming. We've heard about patents, copyrights, trade secrets, and even trademarks, and vague "intellectual property rights". But the actual complaint they filed with the courts does NOT allege any copyright infringement, just breach of contract and unfair competition.

    1. Re:How do you know what they're claiming? by ascii27net · · Score: 5, Informative

      This article on C|Net offers some insight on what they are claiming (comments from Darl McBride in the article): "The System 5 source code, that is really the area that gives us incredible rights, because it includes the control rights on the derivative works that branch off from that trunk." They are claiming that because they have rights over derivative works, everything IBM wrote for AIX is under there control, so IBM can't take code IBM wrote and distributed with AIX in Linux beause it is a derivative of SCO code. That bascially is a claim that they own everything ever writte n for a Unix platform. They even mention JFS - that isn't exactly an SCO technology - but they claim it is a derivative work. "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" "They were going to take the know-how, the people, the methods they developed over the years around AIX--which is our licensed version of Unix--and they were going to transport all that in a wholesale fashion over to Linux." How dare IBM port thier code for AIX to Linux!

    2. Re:How do you know what they're claiming? by swillden · · Score: 4, Informative

      Sounds like SCO's definition of "derivative works" is similiar to that of the GPL.

      Absolutely not. The parallel you're drawing is this: IBM wrote code that was used with and linked to SCO code, and SCO is claiming that they, therefore, have some rights to what is done with the other code that IBM wrote based on expertise they gained working with the SCO code. From a very naive viewpoint, you can say: "See, SCO's code 'infected' IBM's code (and engineers), just like GPL'd code 'infects' code that it touches." But you'd be wrong.

      The GPL does not prevent you from taking code you wrote in one context and using it elsewhere. If you own the copyright, you can release it as many times as you like under whatever terms you like. So it *certainly* doesn't limit what you can do with new code that you write, even if it happens to draw upon expertise you developed while enhancing the GPL code.

      For that matter, the GPL doesn't even prevent you from reading someone else's GPLd code, understanding their nifty, super-cool algorithm and implementing it yourself in your own, closed software. As far as the GPL is concerned, if you wrote it, you own it, no matter where you got the ideas from. Where the GPL gets sticky is when you want to distribute a closed version of something that contains code someone else wrote, and that is perfectly sensible: the fact that you may have written some parts of it doesn't give you the right to violate the wishes of the owner(s) of the rest of it.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    3. Re:How do you know what they're claiming? by swillden · · Score: 4, Informative

      Yet there seems to be this idea in the software development community that even reading someone else's source code will "contaminate" your mind, and make you unable to write a similar program without infringing on copyright.

      Yep. I understand how this mentality arose, but it sure is unfortunate.

      It arose simply because (a) code is functional and (b) lawyers are conservative. Since form follows function, independently-written routines that do the same thing will often be similar, and sometimes look extremely similar. This means that it may, at times, be hard to prove that you wrote a piece of code if someone else happens to have highly similar code that predates yours.

      Attornies (notably, Compaq's attornies back when they reverse-engineerd IBM's BIOS) saw this problem and devised a sure-fire solution: If we can show that the programmers who wrote code B never saw code A, then it's clear that B isn't a copy of A, not even some sort of "inadvertent copy". Hence the development of "clean-room" reverse-engineering, the notion that the engineers who are "exposed" to A are "contaminated" and can't work on B, etc.

      It made sense for Compaq, since they did *not* want to face IBM's legal dept. in court, but it has left the rest of us with an unfortunately skewed view of copyright as it pertains to code.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  60. Re:Maybe Linus is going to 'santize' linux.. by molnarcs · · Score: 5, Informative
    "OS X is BSD, not a line of SysV in the beast, correct?" According to an interview with BSD core developers:
    M. Warner Losh : The code was *NOT* derived from System V, but rather from Unix 6th and 7th edition, as well as 32V. Only the copyrights were similar to those used in System V source files. The code in question was merely blessed by USL and acknowledges as originating there by the Regents. Read here.
    and...
    There never was any System V code in any BSD. Ever. The IP claims that USL made its 1992 suit were based on the inclusion of sixth and seventh editions and 32V. While these were the forerunners to System V and System III code bases, they are not specifically System V or System III. Furthermore, SCO released, under its ancient unix program, all sources that predated System III and System V to be freely distributed under a BSD-like license. These specifically included 6th edition, 7th edition and 32V.
    Read the rest of the interview here.
  61. Re:SMP? RCU? by vinsci · · Score: 4, Informative
    None of that really matters, though, as it seems RCU technology is now public domain, due to the expiration of the patent US4809168, "Passive serialization in a multitasking environment".

    Thanks to xyote for pointing this out:

    "Even IBM doesn't own it. It's in the public domain. Because it was invented by IBM 3 times (hey, it's a big company). Once in the mid 80's in VM/XA Rel 2 (patent 4,809,168 now expired), once at Sequent which was acquired by IBM and where RCU was coined, and once as part of the K42 project at IBM research."
    --

    Trusted Computing FAQ | Free Dawit Isaak!
  62. An Idea by colk99 · · Score: 4, Insightful

    make sco.slashdot.org and allow us to filter this stuff off the home page I have had enough of all the sco stories for a while

  63. SCO: axis of evil? by sterno · · Score: 4, Insightful

    If you want to understand SCO's situation, look at the statements they make and then compare them to the statements North Korea makes. SCO is the corporate equivalent of a starving soviet state, desperate to hold onto its power. The only thing left in its arsenal are threats to use weapons with potentially catastrophic side-effects. Essentially, in both cases it's a plea for economic aid and recognition, and it all demonstrates a tremendous fear that the end is nigh.

    --
    This sig has been temporarily disconnected or is no longer in service
  64. Re:/. pathetic response by Zathrus · · Score: 4, Insightful

    We know well the weaknesses in SCO's claims, but what are the strengths?

    That's the issue... thus far there haven't been any strengths found. The lawsuit is rotten at the core -- the original statement was that IBM leaked SCO trade secrets regarding a number of enterprise level features to Linux. The problem is, each and every one of those features existed in Linux prior to IBM's involvement. It's very hard to have a strong house when your foundation is rotten.

    Has anyone, besides SCO, looked at the Linux code and tried to determine what might have come from SCO, and what might have come from a common predecessor?

    No, because it's an impossibility to do that. SCO is now claiming hundreds of thousands of lines... you can probably look at the whole of Linux and say "well, yeah, the idea for that came from XYZZY", but that's irrelevant - you can't copyright an idea.

    How can the FUD be countered?

    It's difficult to do so if done right. But thus far SCO hasn't been getting many people buying into their FUD. Infoworld, eWeek, CNet, etc. are all casting aspersions on SCO's claims - none are saying that you should shy away from Linux. The only analysts that are saying that are ones that were already in SCO's (or MS's) pockets... and if your management listens to them then you weren't ever going to go to Linux in the first place.

    If SCO wins, what can be done? What will the consequences be?

    Violating code will have to be removed. That's it. That's all that SCO can do -- even in the case of copyright violation (which they're STILL not claiming), all they can do is request cessation of further infringement. They dropped the ball on this one when they didn't properly register the transfer of copyright from Novell -- without that filing you cannot sue for damages or any other monetary amounts -- only for cessation. US law is very, very clear on this.

    IBM will act in its own interests, of course, and not in the interests of the Linux community; what should we expect from them?

    Expect nothing but that they'll do what you say - act in their own best interests. But SCO has acted stupidly here too -- they're trying to back a grizzly bear into a corner. What the hell are they expecting? Statements like revoking AIX's license, that AIX customers are now in violation, claiming IP that belongs to IBM (RCU), etc. are doing nothing but insuring that IBM will go to court to protect their most valuable assets - their customer base and their IP. SCO isn't just backing the grizzly into a corner, it's getting between a mother and its cubs. If they don't change their tune fast they're going to be very unhappy with the outcome.

    How time-consuming would it be to replace all SCO code (if it does exist)? Should it be done now, with all the code they claim regardless of merit, to preempt their case?

    Again, that's impossible to judge. SCO hasn't stated what's allegedly in violation. You can't replace that which you don't know. To even speculate on this is to do nothing but further SCO's FUD.

    Is including controlled technologies in Linux the equivalent of violating US export laws? That could have implications far beyond SCO's suit.

    SMP isn't a controlled technology. In fact, the only software that is controlled is crypto. All of that work is done outside of US borders and is not subject to US export laws, period. Additionally, SCO kickstarted the SMP development in Linux itself by donating an SMP capable motherboard to Alan Cox (who is a citizen of England, also not under US export restrictions). They're the ones who would be liable in such a case, not IBM.

    Export restrictions are predominantly for hardware, not software (with the exception of crypto mentioned above). SCO is barking up the wrong tree here.

    They may seem like critical issues, but the reality is that there's still no basis in reality for most of them. The ones that might be an issue (copyright or trade secret infringement) have no backing behind them yet -- and until SCO puts forth actual documentation regarding it it's not a critical issue. It's just FUD.

  65. What lawsuit ? by AftanGustur · · Score: 4, Informative


    why spend the money on fighting the lawsuit or paying a settlement - buy out SCO

    SCO hasn't sued anybody yet..

    And if their behaviour can be used as a indicator of how solid their case is, I'd say here is a good change they won't be suing anybody in the forseeable future.

    Either that, or the case will be dismissed right after SCO has explained it's case and the judge has had a good belly laugh ..

    --
    echo '[q]sa[ln0=aln80~Psnlbx]16isb572CCB9AE9DB03273snlbxq' |dc
  66. SCO isn't scared at all. by RoLi · · Score: 5, Funny
    Dear IBM!

    We have now identified lots of code copied source from our precious SCO Unix.

    Here are 2 of the worst offending code snippets:

    kernel/sched.c: n++;
    kernel/signal.c: ++count;

    Please look at our SCO-Unix code, you will see how shamelessly those lines were copied:

    drivers/scsi.c: n++;
    drivers/keybd.c: ++count;

    And there are 58 other lines of shamelessly copied source code in Linux. Our marketing department has calculated that each line of code is worth 50,000,000 $ which translates to an average of about 10,000,000$ per character. We have found copied characters worth of 5,693,340,000,000 $ in the Linux source code, however, because we are generous, we only insist on the fully copied lines of code. However, if IBM doesn't pay, we might be forced to demand the full amount.

    But for now, I only demand IBM to pay 3,000,000,000 $ within 2 weeks to this account:

    account holder: Barl McDride
    account no: 4239573204
    Royal Cayman Bank
    134 Ocean Boulevard, Cayman Islands

    Every week of delay will cause another 1,000,000,000 $ due to lost sales, mental stress and other damages which have to be paid to the same account, so please pay quickly, or else.

    Sincirely, your pal

    Darl McBride

  67. MOD PARENT DOWN!Re:They must really be scared now. by sfsp · · Score: 4, Interesting

    Bullshit.

    I lived in Utah for 17 years. I am not a Mormon, and am more opposed to the Mormon Church than I am to Microsoft.

    What you have said, sir Coward, is blatantly offensive to not just Mormons, but to anyone who holds a religious faith. If you hold to a religious faith, you should be doubly ashamed of yourself. If you are going to criticize a person or a group, have the honor to name yourself, your problem, and the group or person you criticize.

    Next time the account creation mechanism doesn't work, try simply signing your name.

  68. Brilliant... by MosesJones · · Score: 4, Funny


    Well I'm English so as a country I hearby give notice that all people in the world who are using English are breaking copyright and all derivative works (including technical specifications and patent applications) are now owned by the UK Goverment.

    We are also claiming Charles Babbage and all derivative works that involve computation and concepts of automated computing.

    Unfortunately the Iraqi's are now claiming that they invented writing, the Chinese are laying claim to printing and basically everyone on without a 2,000 year+ history is screwed.

    --
    An Eye for an Eye will make the whole world blind - Gandhi
  69. IBM won't settle by siskbc · · Score: 5, Insightful
    I personally think that this is SCO trying to get IBM to buy them out. Trying Violently.

    Damn straight it is - Darl accidentally played his hand (or on purpose, who can tell with him) in an interview where he admitted that a buyout from IBM is "an option." That means he asks Jesus for a buyout every night. This guy's just a corporate raider - he has stock options, which are worth a lot more after this lawsuit talk, and he just wants to negotiate a sweet per-share buyout to make them worth even more. Of course, IBM would shitcan all the SCO employees if they did buy them out, including Darl, but he doesn't care. Nice.

    Problem is, IBM won't settle, as they're pissed. Also, if they were to settle, that would only encourage every other dipshit company with some marginal IP and no business plan to pull an SCO. IBM seems to be playing the "we don't negotiate with terrorists" bit, and I don't blame them.

    Also, as SCO has virtually no chance of winning, settling doesn't make financial sense. Naturally, THAT'S why SCO increased the suit to $3B - it lets IBM think that settling makes sense now at a lower SCO success rate. If the break-even point for a settlement was a 50% chance of SCO victory, now it makes sense at a 17% chance. For example, obviously, as both numbers are too high. ;)

    Bottom line, though, is that SCO picked on the wrong dog. This one's gonna eat 'em.

    --

    -Looking for a job as a materials chemist or multivariat

    1. Re:IBM won't settle by Stephen+Samuel · · Score: 5, Funny
      Also, as SCO has virtually no chance of winning, settling doesn't make financial sense. Naturally, THAT'S why SCO increased the suit to $3B - it lets IBM think that settling makes sense now at a lower SCO success rate. If the break-even point for a settlement was a 50% chance of SCO victory, now it makes sense at a 17% chance. For example, obviously, as both numbers are too high. ;)

      the 17% solution only makes sense if SCO has a minimal chance of winning the suit and gettint a reasonable percentage of what they're claiming. Right now, they're suing IBM for GPL'ing a piece of code that (as far as I can tell) was created by a sequent -> IBM employee (and, I presume, assigned to Sequent then transferred to IBM).

      This is my quick summary of the SCO conversation:

      SCO: Stop selling UNIX or we'll sue you to stop you.
      IBM: Why? We have a license!
      SCO: Because you've done something wrong, and you won't fix it.
      IBM: What have we done wrong?
      SCO: We Can't tell you (na na na na naaaa!)
      IBM: You have to tell us what we did wrong if we're going to be able to fix it.
      SCO: We could let one of your engineers see the code we think you stole, but then you'd have to shoot him
      IBM: Can we subpoena your therapist in the counter suit?
      SCO: OK: It's the RCU code. By the way, we're tripling our damages.
      IBM: But we wrote that!
      SCO: And your point is????
      IBM:I don't think we'll be needing your therapist.
      --
      Free Software: Like love, it grows best when given away.
  70. Re:true by shotfeel · · Score: 4, Funny

    I love it when the news media expecially on the internet writes articles and title's them differently everytime they add a paragraph and update the report.

    Too bad we can't get them to do it the right way, with version numbers and ReadMe's stating changes since the previous version.

  71. ONE [ HUNDRED ] BILLION DOLLARS! by saikou · · Score: 5, Funny

    Planning meeting in Dr. Evil's lair.

    Dr.Evil: .... ozone layer
    Number Two: That already happend.
    Dr.Evil: Sh.t! Oh well, let's draft some frivolous lawsuit and sue the world's biggest computer company for...
    ONE MILLION DOLLARS!
    Number Two: *cough* Don't you think we should ask for more?
    Dr.Evil: OK. And sue them for ONE BILLION DOLLARS!
    Or heck, make it three.
    Good.

  72. We asked about that in the IBM interview last year by delcielo · · Score: 4, Informative

    2) OS Blending
    by 2names

    As Linux developers inside IBM, do you get to see the AIX source code? If you do, are you allowed to "steal" some ideas from AIX and implement them in Linux? If not, why not, and what's the IBM official line?

    IBM Kernel Hackers:

    First of all, before any of us were allowed to contribute to Linux, we were required to take an "Open Source Developers" class. This class gives us the guidelines we need to participate effectively in the open source community - both IBM guidelines and lessons learned about open source from others in IBM.

    We are definitely not allowed to cut and paste proprietary code into any open source projects (or vice versa!). There is an IBM committee who can and do approve the release of IBM proprietary or patented technology, like RCU.

    That covers "stealing" code, but what about ideas? We might talk to an AIX programmer and comment we're seeing performance issues in Linux in this area or that area and she tells us they discovered that they really needed to profile the network routines when they saw that. Having solved the problem once, our non-Linux peers can help steer us without spelling it out for us, allowing us to still develop solutions that can then be open sourced.

    It's a fine line to walk, especially as an engineer who just wants the answer :)

    Interview

    --
    Hot Damn! It's the Soggy Bottom Boys!
  73. SCO Unix in Iran by roozbeh · · Score: 4, Interesting

    The suit also adds illegal export issues stemming from the worldwide availability of open-source software. SCO claims IBM has breached its contract by making multiprocessor operating system technology available "for free distribution to anyone in the world," including residents of Cuba, Iran, Syria, North Korea and Libya, countries to which the United States controls exports. The open-source technology IBM released "can be used for encryption, scientific research and weapons research," the suit said.

    Guess what? SCO Unix is already used widely in Iran. I can confirm it. I live in Iran.

    So perhaps it's SCO itself that is breaking the US export regulations.

  74. Re:News Flash from Next Week by SubtleNuance · · Score: 4, Insightful

    Really, what is the US coming to? With VERY little research, a foreigner, like myself can discover this is conservative propagnada. Al Gore Never said he "invented the internet". He did say, "During my service in the United States Congress, I took the initiative in creating the Internet."

    Regarding that statment; Vincent Cerf, who's been called the Father of the Internet, said "The Internet would not be where it is in the United States without the strong support given to it and related research areas by the Vice President in his current role and in his earlier role as Senator."

    The inventor of the Mosaic Browser, Marc Andreesen, credits Gore with making his work possible. He received a federal grant through Gore's High Performance Computing Act.
    The University of Pennsylvania's Dave Ferber says that without Gore the Internet "would not be where it is today."

    Joseph E. Traub, a computer science professor at Columbia University, claims that Gore "was perhaps the first political leader to grasp the importance of networking the country. Could we perhaps see an end to cheap shots from politicians and pundits about inventing the Internet?"

    So, what Gore said was "true" according to Traub, Ferber, Andreesen, and Cerf.

    This "story", can be read about here: http://www.perkel.com/politics/gore/internet.htm

    Bottom line, please DONT spread this meme, its flatly untrue... but the fact that this story "Has Legs" in the US is not surprising, when you read here (please read this..) that One in three Americans believe WMD have been found in Iraq. Nearly one in four Americans believe Iraq actually used WMD in the war. And half of those polled in a survey said Iraqis were among the 19 hijackers on Sept. 11, 2001.

    With the US so poorly informed, its no wonder Shrub runs willy-nilly around the planet... WHAT IS WRONG WITH THE USA?

  75. Re:/. pathetic response by bwt · · Score: 5, Informative

    Has anyone, besides SCO, looked at the Linux code and tried to determine what might have come from SCO, and what might have come from a common predecessor?

    So far four components of the Linux source have been implicated: SMP, RCU, NUMA, and JFS.

    I have done a little digging into the NUMA code. IBM has contributed several people who have participlated in developing NUMA under linux. Some names I've run across: Martin Bligh, Matthew Dobson, Patricia Gaughen, John Stultz, Michael Hohnbaum. IBM even has a Linux NUMA news archive. It appears that IBM jumpstarted it's NUMA efforts when it purchased Sequent which was intitally intended to boost its participation in Project Monterey, which is no doubt the origin of SCO's objections.

    The most obvious source file for NUMA is /usr/src/linux/mm/numa.c in the 2.4 series kernels. This file contains a comment header stating it was "Written by Kanoj Sarcar, SGI, Aug 1999". This file has been removed from later 2.5 kernels (its gone by at least 2.5.46), appearently because Linux accepted an IBM NUMA patch as reported here. This patch was announced by Martin Bligh and is likely the code in question in this lawsuit.

  76. Evil Genius For Dummies by Tony · · Score: 5, Interesting

    As is apparent by this post, IANAL, I have never wanted to be a lawyer, nor do I have any respect whatsoever for the lawyer profession. Fucking weasels.

    That said:

    SCO is not claiming copyright infringement, so the case isn't strictly about copied code. They are claiming violation of contract, so the *court case* will hang on contract law, *not* IP law.

    However, in *public* they are making this an IP case. They have made not-so-veiled claims to owning the rights to the concepts of *all* modern operating systems.

    If the case were based on their public claims, they wouldn't stand a chance. But, their case is based strictly on contract law. All this public posturing means nothing.... except....

    If they win the contract violation suit, it will appear as if their public claims were valid, and upheld by the force of law!

    This is subtle, and will have a chilling effect on all future SCO dealings. They can then extort money from every single OS vendor in the country, based not on actual fact, but on lies and innuendo. Look at how quickly (Sun?) and Microsoft payed up without a single court win.

    In any case, this public face is designed to get the top administration a chance to sell their shares at a nice profit. They don't really care about much else, near as I can tell.

    Fuckers.

    --
    Microsoft is to software what Budweiser is to beer.