Slashdot Mirror


SCO Fails to Produce Evidence

BlueSteel writes "For those of you that need that daily SCO fix, Groklaw has the declaration of Ryan E. Tibbitts of SCO, stating why they haven't produced any evidence... and that they need recent AIX and Dynix/ptx code from IBM before they can comply."

71 of 651 comments (clear)

  1. uh.. by grub · · Score: 5, Funny


    For those of you that need that daily SCO fix

    Daily? Has /. been cutting back?

    --
    Trolling is a art,
    1. Re:uh.. by Webmonger · · Score: 5, Funny

      Daily? Has /. been cutting back?

      No. See today's story, for example. Oh, wait...

    2. Re:uh.. by Frymaster · · Score: 4, Funny
      Daily? Has /. been cutting back?

      1. well, it has been the holidays and
      2. if you want your sco stories to be delivered on time, ibm will have to hand over some code from aix first.

    3. Re:uh.. by Anonymous Coward · · Score: 5, Funny

      From bash.org #106579
      Topic in #os: hey guyz, stop pickin on irix.
      <SCO> w00t! i bought unix! im gonna b so rich!
      <novell> /msg atnt haha. idiot.
      <novell> whoops. was that out loud?
      <atnt> rotfl
      <ibm> lol
      <SCO> why r u laffin at me?
      <novell> dude, unix is so 10 years ago. linux is in now.
      <SCO> wtf?
      <SCO> hey guyz, i bought caldera, I have linux now.
      <red_hat> haha, your linux sucks.
      <novell> lol
      <atnt> lol
      <ibm> lol
      <SCO> no wayz, i will sell more linux than u!
      <ibm> your linux sucks, you should look at SuSE
      <SuSE> Ja. Wir bilden gutes Linux fur IBM.
      <SCO> can we do linux with you?
      <SuSE> Ich bin nicht sicher...
      <ibm> *cough*
      <SuSE> Gut lassen Sie uns vereinigen.
      * SuSE is now SuSE[UL]
      * SCO is now caldera[UL]
      <turbolinux> can we play?
      <conectiva> we're bored... we'll go too.
      <ibm> sure!
      * turbolinux is now turbolinux[UL]
      * conectiva is now conectiva[UL]
      <ibm> redhat: you should join!
      <SuSE[UL]> Ja! Wir sind vereinigtes Linux. Widerstand ist vergeblich.
      <red_hat> haha. no.
      <red_hat> lamers.
      <ibm> what about you debian?
      <debian> we'll discuss it and let you know in 5 years.
      <caldera[UL]> no one wants my linux!
      <turbolinux[UL]> i got owned.
      <caldera[UL]> u all tricked me. linux is lame.
      * caldera[UL] is now known as SCO
      <SCO> i'm going back to unix.
      <SGI> yeah! want to do unix with me?
      <SCO> haha. no. lamer.
      <novell> lol
      <ibm> snap!
      <SGI> :~(
      <SCO> hey, u shut up. im gonna sue u ibm.
      <ibm> wtf?
      <SCO> yea, you stole all the good stuff from unix.
      <red_hat> lol
      <SuSE[UL]> heraus laut lachen
      <ibm> lol
      <SCO> shutup. i'm gonna email all your friends and tell them you suck.
      <ibm> go ahead. baby.
      <SCO> andandand... i revoke your unix! how do you like that?
      <ibm> oh no, you didn't. AIX is forever.
      <novell> actually, we still own unix, you can't do that.
      <SCO> wtf? we bought it from u.
      <novell> whoops. our bad.
      <SCO> i own u. haha
      <SCO> ibm: give me all your AIX now!
      <ibm> whatever. lamer.
      * ibm sets mode +b SCO!*@*
      * SCO has been kicked from #os (own this.)

    4. Re:uh.. by red+floyd · · Score: 4, Funny

      Not bad, but you forgot the line

      * SuSE[UL] is now novell[SuSE]

      --
      The only reason we have the rights we have is that people just like us died to gain those rights. -- Cheerio Boy
    5. Re:uh.. by NickDngr · · Score: 5, Informative

      That's really good. Even though +5 Funny doesn't help Karma, I would have wanted that one under my belt anway - why did you post as AC??

      Because I copied it from bash.org, and I didn't want to take credit for it.

      --
      Yoda of Borg am I! Assimilated shall you be! Futile resistance is, hmm?
    6. Re:uh.. by Lane.exe · · Score: 4, Funny
      You forgot:

      [SuSE] Herr Mandrake, willst du mitgekommen?

      [Mdk] Je ne sais pas. Peut-etre je me rendrai juste a la faillite.

      [SuSE] Na ja.

      --
      IAALS.
  2. Summary by GnrlFajita · · Score: 5, Informative
    In case you don't want to RTFA, it all boils down to SCO giving two excuses for not fully complying with the court's order:
    (1) Hey, it was the holidays. This lawsuit isn't important enough to bother our directors with over Christmas.
    (2) Well, we're pretty sure that they're infringing somehow, but despite the fact that we claim to own this stuff, doggone if we can't find a current version of it. Anyway, once IBM spells it all out for us I'm sure we'll come up with something that looks like that other thing. Probably.

    Another FA you can avoid R'ing (link found at Groklaw): the Motley Fool looks at the 'shakedown' of Linux providers: "with the entire computing world putting its money behind Linux, it appears that, for SCO, the apocalypse is now."

    --
    When we remember we are all mad, the mysteries disappear and life stands explained.
    Mark Twain
    1. Re:Summary by IFF123 · · Score: 5, Funny

      But why should we provide the code and go into court when we can sue users and companies right now?

      --
      Who took my tinfoil hat?
    2. Re:Summary by Daniel_Staal · · Score: 5, Insightful

      (Disclaimer: SCO is smoking crack. I believe none of what I am about to say...)

      Actually, SCO has a point. They claim ownership of the code in UNIX derivatives, of which AIX and the rest are examples. The fact that SCO has never seen or handled that code in any way is irrelevant. It is perfectly possible that IBM has infringed on SCO's property by copying code that IBM wrote for AIX/others into Linux. In which case, the only copy that SCO currently has access to is the Linux copy. After all SCO didn't write the code. IBM did. SCO just owns the rights.

      --
      'Sensible' is a curse word.
    3. Re:Summary by cduffy · · Score: 5, Informative
      Yup. And that would be true, too, if it weren't for the letter of understanding to the contrary; see Exhibit C from here:
      "3. Regarding Section 2.01, we agree that modifications and derivative works prepared by or for you are owned by you. However, ownership of any portion or portions of SOFTWARE PRODUCTS included in any such modification or derivative work remains with us."
      This makes it pretty darned clear that IBM does in fact own their own "modifications and derivative works", which covers JFS and all the other features IBM added to AIX (and later Linux).
    4. Re:Summary by AKAImBatman · · Score: 4, Informative

      Actually, that's wrong. IBM's contract specifies that original code added to Unix by IBM is IBM's property. SCO has been ignoring this clause by trying to redefine what "derivative" means. Unfortunately (for them), there's a huge case history of derivative works that have already established that SCO can't redefine derivative to mean what they want it to mean.

      Ergo, SCO is smoking crack.

    5. Re:Summary by k12linux · · Score: 4, Insightful
      The linux development goes on more or less as usual... less some time for Linus or others to take interviews from the press. IBM's Linux development is very likely moving at the same pace it always had.

      They may have taken steps to ensure that current programmers had never had any access to protected UNIX or AIX code, but I doubt it goes much further than that.

      Surveys show that adoption of Linux is being affected very little by this thing.

      IBM already has enough lawyers to darken the skys and a few million $ spent probably will be more than offset by the press and PR of it all when things are finally settled.

      As far as I can see only SCO is really being affected. They haven't produced anything new for some time so that's notthe issue... but according to their SEC filings, this thing is costing them millions. (Something like $9 million in the last quarter alone.)

    6. Re:Summary by 0WaitState · · Score: 4, Interesting

      The problem with that is you cannot just bring suit to compel a company to open up its proprietary code for you to check for violations. You have to make a realistic case that there are violations *before* getting access. Otherwise, what's to stop every out-of-work coder from bombarding software companies with nuiscance lawsuits saying "You used my sekrit weeblefetzer quicksort variation without a license! Spend $500,000 responding to my demands for evidence or settle (buy a license) for $69,900!"

      --

      Remain calm! All is well!
    7. Re:Summary by Sj0 · · Score: 4, Informative

      IBM probably keeps those lawyers on the payroll, so I wouldn't be suprised if the lawsuit isn't costing them a penny. You do that sort of thing when you're oh my god huge. :)

      --
      It's been a long time.
    8. Re:Summary by rgmoore · · Score: 5, Informative
      Of course, IBM has shown evidence that their contract does NOT say otherwise, but SCOldera seems to be hoping that the judge will overlook that tiny detail. :)

      Except that's not quite right. The truly pathetic side to this story is that it isn't IBM that produced the evidence that the license doesn't say what SCO claims it does. It was SCO. That's right, they attached the side letter (as Exhibit C) establishing that IBM had rights to their own work to their original complaint. It's still right there on their website. Their own evidence debunks the main theory behind their case!

      --

      There's no point in questioning authority if you aren't going to listen to the answers.

    9. Re:Summary by michael_cain · · Score: 5, Insightful
      This makes it pretty darned clear that IBM does in fact own their own "modifications and derivative works"

      I think SCO's case -- the real case, the one that has to be argued in court -- will acknowledge that IBM owns their own work, and that they can do anything they want in terms of embedding it in binary form in their own products, but that IBM requires SCO's permission to reveal the source code or even the methods used to third parties. That's a fairly fine distinction. There are lots of situations where you own something, but there are constraints on the uses that you can make of it. I think SCO will lose, mostly on grounds that (a) most of the SysV "trade secrets" aren't, (b) the previous owners of the contract didn't adequately protect their trade secret rights (so SCO can't successfully attempt to reclaim those rights), and (c) neither party who signed the contract in 1985 intended for it to apply this far into the future.

    10. Re:Summary by c1ay · · Score: 5, Interesting
      Somebody please tell me what I'm missing here. In an interview with CNET Darl Mcbride says, "We're finding...cases where there is line-by-line code in the Linux kernel that is matching up to our UnixWare code," In addition, he said, "We're finding code that looks like it's been obfuscated to make it look like it wasn't UnixWare code--but it was."

      Now Mr. Tibbits says they need recent AIX and Dynix/ptx code from IBM before they can comply.

      Have they identified offending lines in the kernel source or have they not. Darl claims they have already matched code to the Unixware code and now they can't seem to reproduce it for the court. What's wrong with this picture?

      --

    11. Re:Summary by mst76 · · Score: 5, Informative
      Have they identified offending lines in the kernel source or have they not. Darl claims they have already matched code to the Unixware code and now they can't seem to reproduce it for the court. What's wrong with this picture?
      There are two different issues. 1. IBM contributed SMP, JFS, RCU, and NUMA code to linux. SCO claims these came from from AIX, and that they have right to everything IBM adds to AIX. They are sueing IBM for contract violation, not copyright infringment. They do not need to show any copied lines, only that the mentioned code come from AIX and that their original Unix contract gave them right over these technologies. 2. SCO claims in the press that they discovered line by line copying from SystemV in the Linux source code. They sent letters to companies, threatening to sue them if they don't buy a license from SCO. They show these lines to journalists and developers under NDA. They have NOT actually gone to court over this, so they do not actually need to prove copyright infringment. They are intentionally refering to both actions as "defending their IP". The idea is that since they have actually gone to court over one issue, the companies who received the letters for protection money will find their other threats more credible.
  3. Amazing by MoxCamel · · Score: 5, Funny

    Well, tip me over with a feather! I never would have seen this coming!

  4. Shock horror! by Trejkaz · · Score: 5, Funny

    Oh no! SCO couldn't produce any evidence! Maybe that's because THERE IS NO EVIDENCE!

    --
    Karma: It's all a bunch of tree-huggin' hippy crap!
    1. Re:Shock horror! by Anonymous Coward · · Score: 4, Funny

      Hey, lack of evidence worked in Iraq... why not here?
      -bk

    2. Re:Shock horror! by boaworm · · Score: 5, Funny

      Maybe that's because THERE IS NO EVIDENCE!

      Exactly. That's why they need more time. to PRODUCE the evidence :-)

      --
      Probable impossibilities are to be preferred to improbable possibilities.
      Aristotele
    3. Re:Shock horror! by red+floyd · · Score: 5, Insightful

      #include
      It's worse than that. In the 5 December hearing, the judge ruled that they can't ask for ANY of IBM's stuff until they provide answers to IBM.

      Tibbets' declaration seems to say, "give us the stuff you said we can't have, and then we'll give you the stuff you told us we had to provide".

      --
      The only reason we have the rights we have is that people just like us died to gain those rights. -- Cheerio Boy
    4. Re:Shock horror! by ehvoy · · Score: 5, Funny

      true. HOWEVER, if chewbacca is a wookie, you must pay $699...

      what was the gist of the south park episode again?

    5. Re:Shock horror! by tntguy · · Score: 4, Funny

      However, since the lack infinite time, they'll only be able to produce Windows 2004.

  5. Since when... by mr_mischief · · Score: 5, Insightful

    is it the defendant's job to prosecute himself?

    1. Re:Since when... by jmv · · Score: 5, Funny

      That's the new terrorist laws. Suspected terrorists must prove that the are terrorists. If they fail to provide proof, the are jailed for obstruction to justice.

  6. This just in.. by Anonymous Coward · · Score: 5, Funny

    News just in - the Emperor has no clothes, and - eww - that's disgusting!

    If anyone believed SCO, I hope they feel silly right now...

  7. And it completely unrelated news by LNO · · Score: 5, Funny

    Monkeys failed to fly out of my butt.

    I'm not convinced they're unrelated.

  8. Old version? by lostchicken · · Score: 4, Interesting

    How did SCO get a copy of "IBM AIX source code, an old version labeled MERCED/9922A_43NIA"?

    I doubt that IBM would have just turned over source to AIX as part of the trial, much less an old version, so how did they get it?

    --
    -twb
    1. Re:Old version? by IPFreely · · Score: 5, Informative
      How did SCO get a copy of "IBM AIX source code, an old version labeled MERCED/9922A_43NIA"?

      A few years back, when Intel was first spouting off about Itanium, IBM and SCO were working togethere on a next-generation Unix project targeted at Itanium. That project was called "MERCED". That's most likely where that code came from.

      --
      There is nothing so silly as other peoples traditions, and nothing so sacred as our own.
    2. Re:Old version? by leoxx · · Score: 5, Informative

      You have it almost right. "Merced" was the code name for what is now known as the Itanium CPU from Intel. The code name for the joint IBM/SCO Unix was "Monterey".

    3. Re:Old version? by Anonymous Coward · · Score: 5, Informative

      Actually the chip now called Itanium was originally named Merced. The project between IBM and SCO was Project Monterey. (Note one 'R' - the town in California not too far from Santa Cruz where the deal was signed, not the place in Mexico).

      Project Monterey was going to take the best bits of SCO UnixWare (basically SVR4.2), SCO OpenServer (SVR3.2 but with lots of user/admin friendly stuff which is why people bought $200m of it each year) and AIX (ancient roots in SVR3.2 but thoroughly IBMized), and combine them all into a kick-ass UNIX for Itanium. Itanium was perceived at the time as where the commodity 64 bit chip market was going and the idea was to band together against Sun (Sparc) and Compaq/Digital (Alpha).

      Work did start on Monterey, but the problem was that IBM ended up doing most of the work. It was supposed to be equal, but SCO just did not have the people. (At the time Windows NT and Linux were advancing so quickly that SCO was having a hard time even pretending to be relevant any more).

      SCO ended up doing less and less towards Monterey and eventually IBM just gave up and called it quits.

      Both Windows NT and Linux were eating away at SCO's UNIXes. SCO tried various things such as clustering and data center acceleration programs, but it was a lost cause. There was however some one time revenue from people doing Y2K upgrades, which SCO's able management didn't realise was one time.

      Caldera then got interested in the SCO channel (15,000 mom and pop shops around the world that sold OpenServer in conjunction with other software, hardware and services - think outfitting a dentists office). SCO and Caldera came up with some very convoluted agreement that even the SEC couldn't understand. They then did a second agreement, and all the UNIX stuff when to Caldera, and the original SCO became Tarantella.

      Caldera continued to suck because the 15,000 mom and pop shops did not like being lectured to, and could do Linux by themselves. They didn't need Caldera. Caldera couldn't make money at $24 a copy. Eventually they decided to plunder the OpenServer/UnixWare revenue stream (OpenServer customers are extremely loyal) and came up with various licensing plans noone was interested in.

      Finally they decided to take a gamble on taking on IBM ...

      (Disclaimer: I am an ex-SCO employee, but had nothing to do with any of the crap other than as a highly critical observer).

  9. SCO Attorney: Please, IBM, give us evidence by Anonymous Coward · · Score: 5, Funny

    SCO Attorney: "Your honor, we are unable to provide evidence for our claims. We request that IBM prove our case for us."

    Judge to commence laughing in 5..4..3..

  10. Can't wait... by Mr.+Sketch · · Score: 4, Funny

    to see what IBM's Legion Of Firebreathing Laywers have to say about this.

    [sits back and grabs some popcorn] This should be good...

  11. SCO says: by cybermace5 · · Score: 4, Funny

    "You want the evidence? You can't HANDLE the evidence!"

    --
    ...
  12. D'oh! by frodo+from+middle+ea · · Score: 4, Funny

    D'oh!, I demand a refund of my $699.

    --
    for the last time people, I am "frodo from middle eaRTH", not "middle eaST".
  13. Oh, man, I'm picturing Lionel Hutts by The+I+Shing · · Score: 5, Funny

    Wasn't there a scene in The Simpsons where Lionel Hutts doesn't have any evidence for his lawsuit and he asks the person he's suing if he can help?

    Was it the one where he sued over Itchy & Scratchy?

    He stammers out something like "Well, um, we don't have a copy of it... we were kind of hoping that you did."

    --
    You are in error. No-one is screaming. Thank you for your cooperation.
  14. And from the street... by MSBob · · Score: 4, Funny

    And as should be expected by now, SCOX stock rose on the news today.

    --
    Your pizza just the way you ought to have it.
  15. Increasingly hilarious by bugnuts · · Score: 4, Funny

    SCO: you infringed on our code, we're suing
    IBM: prove it
    SCO: no, you prove it!

    wtf? How did they get this far? I rarely root for the 800 lb gorilla, but it appears the strategy for SCO is just to tie this up in litigation as long as possible.

    There is a different issue here... this has nothing to do with copyright infringement anymore, it is political maneuvering of consumer views. But, I'm preaching to the choir at this point.

  16. Solution by Zork+the+Almighty · · Score: 4, Funny

    Maybe IBM can give them a list of files which infringe ;)

    --

    In Soviet America the banks rob you!
  17. IBM response by pyros · · Score: 5, Funny

    Lawyers arrive in court, head counsel for IBM opens briefcase, pulls out megaphone, points it at Boies, and says in Eric Cartman's voice "Would you like, to suck my balls, Mr. Boies?"

  18. MotleyFool is writing off SCO by MSBob · · Score: 5, Informative

    Expect a significant selling pressure on the SCO stock after this publication.

    --
    Your pizza just the way you ought to have it.
  19. Please Copy and Distribute prosecute-sco.html by MichaelCrawford · · Score: 5, Interesting
    Please copy and distribute Let's Put SCO Behind Bars. It has a Creative Commons license.

    From the page:

    While the lawsuits being defended by IBM and filed by Red Hat are likely to put an end to The SCO Group's menace to the Free Software community, I don't think simply putting the company out of business is likely to prevent us from being threatened this way again by other companies who are enemies to our community. I feel we need to send a stronger message.

    If we all work together, we can put the executives of the SCO Group in prison where they belong.

    If you live in the U.S., please write a letter to your state Attorney General. If you live elsewhere, please write your national or provincial law enforcement authorities. Please ask that the SCO Group be prosecuted for criminal fraud and extortion.

    It also suggests complaining to the securities and exchange commission, which you're entitled to do if you've lost investment money as a result of any wrongdoing that SCO might have committed.

    Thank you for your attention.

    --
    Request your free CD of my piano music.
  20. Question for the lawers among us ... by tmoertel · · Score: 5, Funny
    Would it be considered terribly inappropriate, or even grounds for appeal, if the judge called Darl and Kevin McBride to the bench and then repeatedly, and with extreme prejudice, smote them with her gavel?

    Just curious.

    1. Re:Question for the lawers among us ... by shystershep · · Score: 4, Funny
      I believe that Federal Rule of Civil Procedure 37, which governs discovery disputes, only allows a single smite. Rule 11, on the other hand -- which deals with frivolous filings -- does allow smiting "repeatedly, and with extreme prejudice."

      So I believe the answer to your question would be "please sir (or ma'am), may I have some more?"

      --
      The bigotry of the nonbeliever is for me nearly as funny as the bigotry of the believer. - Albert Einstein
  21. Statements 14, 15 and 16 by grasshoppa · · Score: 4, Funny

    "14. I have been informed by SCO's engineers and consultants that since the only version of AIX source code that was available for comparison purposes is several years old, and predates most of IBM's contributions to Linux, it was not possible to directly compare IBM's contributions to Linux with the most likely source of those contributions, namely the missing versions of AIX (including the most recent versions).

    "15. Further, we have only one CD of Dynix/ptx source code that was produced by IBM, and this CD only contains a limited history of Dynix/ptx releases. It was therefore not possible to directly compare IBM's contributions to Linux with another likely source of those contributions, namely the missing versions of Dynix/ptx.

    "16. Our engineers have reached the conclusion that parts of Linux have almost certainly been copied or derived from AIX or Dynix/ptx. In those cases, confirmation of this opinion would require access to more current versions of AIX and Dynix/ptx.

    Ok, I'm confused. Since when do two false's make a positive.

    Ohh..they must be XORing the system. That makes perfect sense.

    --
    Mod me down with all of your hatred and your journey towards the dark side will be complete!
  22. Re:I'm sure glad... by daeley · · Score: 4, Funny

    Briny Tidbitts

    Sounds like a Spongebob Squarepants character. :)

    --
    I watched C-beams glitter in the dark near the Tannhauser gate.
  23. The Ministry of Truth feels your comments are ... by burgburgburg · · Score: 4, Funny
    doubleplusungood. Representatives of the Ashcroft Ministry of Love will be stopping by later to take you on a vacation to sunny Guantanamo Bay where you can relearn to love Big W.

    Oh, and the chocolate rations have been increased to 5 units.

  24. So they've never had specific proof ! by Performer+Guy · · Score: 5, Interesting

    This is pretty amazing, since they've been claiming all along that Linux infringes and they have proof. When asked for proof they have now said in writing that they can't produce that proof without seeing code they don't have.

    In other words they've never had specific proof.

    So their whole case is apparently hinged upon their tenuous claim to ownership of IBM authored code which they claim they own, but have never seen. They hope they can claim ownership of that code on the basis of a very broad interpretation of derivitive works and that code IBM wrote into AIX was derived (by their incredible definition) from their copyright works (the missing link) and that they then moved this into Linux.

    IANAL but you can't run around claiming someone infringes on your copyrights and then go on a fishing expedition for the evidence, you need something evidence to present to the court in the first place.

    This bubble may burst much sooner than I had anticipated.

  25. Re:Since when... (offtopic) by ozric99 · · Score: 5, Informative
    Since when is it the defendant's job to prosecute himself?

    Not entirely related, however, an interesting facet of UK law as it stands at the moment, when presented with a NIP (Notice of Intended Prosecution) for a speeding charge (taken by a speed camera), the recipient has two choices:
    1. Fill in, sign the form and send it back, thus incriminating yourself.
    2. Refuse to fill it in and get charged with obstruction of justice.

    There is a "loophole" that involves, amongst other things, the defendant returning the form without signing it, going to court, adn finding the police can't use it as evidence. Somethign along those lines, anyway.

    That snippet of our law aside, what SCO are attempting to do would surely be laughed out of every court in teh land. I await the judges decision with baited breath. SCO is going down - of that there's no doubt, however, I wonder whether the main protagonists in this case will be able to walk away scot free under the protection of Canopy. I sincerely hope that won't be the case.

  26. Fiduciary Duty by red+floyd · · Score: 5, Insightful

    Seems to me that RBC (and any other investors) have a decent lawsuit against SCO.

    With a $3Billion (pinky to mouth) lawsuit at stake, the friggin' directors couldn't give up their holiday vacation to provide info that the Court specifically ordered them to? Now, IANAL and IANACPA, but that would seem to be a breach of fiduciary duty!

    --
    The only reason we have the rights we have is that people just like us died to gain those rights. -- Cheerio Boy
  27. Re:I don't understand... by Jahf · · Score: 5, Insightful

    Exactly.

    The court should order SCO and IBM to both put their codes into blind escrow and then release the code from both to the legal team for each so that no funny business can go on =and= so that both sides have equal footing for making their cases. Same for any other participants who have been accused by SCO.

    May not be standard procedure, but this is a rather odd case. It would definitely help both companies show to their customers that they are playing fair.

    Additional code discovery could happen, but it should always be under view of the court.

    --
    It is more productive to voice thoughtful opinions (reply) than to judge (moderate) others.
  28. Obviously by ceswiedler · · Score: 4, Insightful

    This makes it clear that SCO is not talking about old code. They aren't claiming that IBM put ancient SysV code into Linux. They're claiming that they own code that IBM wrote and they never saw (and don't have a copy of).

    If they were saying that AT&T gave IBM the Unix source, and SCO inherited the Unix source, and IBM put the Unix source into Linux, then SCO would have a copy of the source of the infringement. If SCO doesn't have a copy, then that's a damn good sign that they never owned it.

    Clearly their interpretation is that anything IBM ever wrote related to UNIX is covered by their new UNIX copyright.

    Does George Lucas own the copyright to every Star Wars book ever published--say, the Timothy Zahn trilogy?

  29. Improper initial statement by Damn_Canuck · · Score: 4, Informative

    Just a correction for the initial post: SCO has claimed that they have submitted much of the material to IBM, just not all (this is verified by the statements of Mr Tibbitts). The information they do not yet have are for those managers who were on vacation and couldn't get the papers to their legal dep't before they went away for, what, a month??? But definitely keep an eye on the Groklaw site. They get all the information as soon as it is available and is a great site to find all the SCO info. (For those who don't get enough at /.)

    --
    Given that God is infinite, and the Universe is also infinite, would you like some toast?
  30. New SCO deal by Anonymous Coward · · Score: 4, Funny

    In related news, SCO hires world reknowned magician David Copperfield. Sources close to the deal state that the relation is to ensure that the proof behind all the lawsuits magically appears. Further reports link ties with the leprechaun from Lucky Charms to ensure the end result is magically delicious.

  31. The thing that's most amazing to me.. by schon · · Score: 5, Informative

    Now, this is pretty surprising - you're compelled to produce evidence, and you refuse... that's pretty much just asking for contept charges..

    but put it in context, and it's absolutely mind-bogglingly stupid.

    SCO and IBM have been going back and forth for months on the issue of discovery. SCO keeps saying they need evidence from IBM before they can produce their own proof, and IBM says that they need to know what they're being accused of.

    The judge reads all this crap from SCO (about how they can't prove their case until IBM gives them evidence) and decides that IBM is in the right - but she decides to give SCO the benefit of the doubt.. she tells them "I've read everything you've given me, and you're wrong. Unless you can convince me otherwise, I'm going to force you to comply with IBM's discovery.

    So SCO goes on about how they can't prove their case until IBM gives them evidence - and the judge says "You have failed to convince me. Either you have evidence they did something wrong or you don't, it's shit-or-get-off-the-pot time. You have 30 days to produce evidence to back up your claims. If that's not enough time, tell me now, and I'll extend it."

    SCO says "No, that's enough time."

    So 30 days pass, and SCO's answer is "We can't do it because IBM won't give us the evidence."

    I mean - come on - refusing to comply to a compel order is stupid, but repeating the exact same excuse the judge has already rejected as your reason for refusing to comply is so completely unbelievable it's unreal.

    And then (to salt the wound) they claim they didn't have enough time - after explicitly being asked by the judge if 30 days was enough.

    Is SCO trying to lose on purpose?

  32. I hope not by roystgnr · · Score: 4, Interesting

    I hope SCO spends itself out of existence on legal fees.

    That would be awful both for Red Hat and IBM (who should otherwise be getting some amount of reparations in their countersuits) and for SCO's current investors, some of whom probably imagine that the US has a swift justice system that wouldn't allow SCO to make outright lies without sanction.

    Reserve your ire for SCO's current leaders, particularly the ones whose insider trades (filing to buy stock options and sell shares after SCO's internal discussion of the IBM litigation but before that litigation became public knowledge) and deception have earned them millions of dollars so far. These guys are next to the Enron executives in the United States' ongoing experiment: "How hard is it to profit from million dollar lies and escape punishment?"

  33. Information content analysis by El · · Score: 5, Funny

    SCO not producing evidence isn't news. If SCO actually produced some valid evidence, now THAT would be news! In information theory, the information content of an event is inversely proportional to the probability of that event occuring. Since the probability of SCO not producing evidence is 1 for all practical purposes, the message "SCO has not produced evidence" has an information content of zero.

    --

    "Freedom means freedom for everybody" -- Dick Cheney

  34. Not exactly true by Anonymous Coward · · Score: 5, Insightful

    Maybe in legal terms, but while SCO has technically complied to the order, it was legal for them to do so without producing much evidence. Which apparently they did. 60 pages surely doesn't cover the millions of lines of code they were talking about in the press. A confident litigator would not accompany his case with an excuse-note saying that they don't know what the hell's going on, but they have just a suspicion.

    So, while they have complied in legal terms, they have weakened their case in a significant order of magnitude. Not only that, but they have also weakened their case for any of their prosprective targets in their scoSource shakedown fiasco.

    Maybe inaccurate on a legal basis, but significant when looking at the big picture.

    I read Groklaw as well by the way.

  35. Seems thier case is going to sink or swim by fw3 · · Score: 4, Interesting
    *Entirely* on the 'derivative works' theory.

    I (we) uniformly disagree on the theory that everything IBM added to AIX must not also be added to Linux. Because substantive technologies are not derivative works, specifically:

    1. IBM pretty clearly took a very safe path with JFS, it came from the os/2 version (and I bet they read GPL and forsaw these issues before porting to Linux)
    2. IBM almost certainly did not develop only in the context of AIX/systemV license (i.e. they use jfs, NUMA etc on other platforms),

    However, to devil's-advocate this:

    Device, filesystem drivers used with Linux may be considered derivative works, even if not shipped with the Linux distribution, and therefor subject to GPL. *Linus* has said exactly this, and while I personally doubt that SCO is going to prevail (see contract details between AT&T/Novell/SCO/IBM which decidedly establish that this type of additions are not restricted to confidentiality or considered deriviative works.

    Which means basically that if the FSF had licensed a GPL Unix to IBM, they would right now be taking the reciprocal (but logically identical) position as SCO is with respect to license requirements.

    I continue to think SCO loses (and continues to look like halfassed morons), with this tack but remember the Linux community does apply similar logic around IP.

    --
    Linux is Linux, if One need clarify their dist: <Dist>/GNU Linux
    bsds are of course just BSD
  36. Re:Gentoo! by Yorrike · · Score: 5, Funny

    It would have been there, but it was busy compiling ; )

    --

    Looks can be deceiving. Or CAN they?

  37. Re:Gentoo! by rsax · · Score: 5, Funny

    Actually.............

    [16:05] gentoo has joined #os
    [16:06] gentoo: PORTAGE IS COOL!! RPM & DEB SUCK ASS!
    [16:06] gentoo: PORTAGE IS COOL!! RPM & DEB SUCK ASS!
    [16:06] gentoo: PORTAGE IS COOL!! RPM & DEB SUCK ASS!
    [16:06] gentoo: PORTAGE IS COOL!! RPM & DEB SUCK ASS!
    [16:07] debian sets mode +b gentoo!*@*
    [16:07] gentoo has been kicked from #os (stop flooding lamer)

  38. IBM: Not exactly "Fire Breathing" by Saeed+al-Sahaf · · Score: 4, Funny
    to see what IBM's Legion Of Firebreathing Laywers have to say about this.

    Not sure if "fire breathing" is quit the right way to describe the IBM guys...

    As we know from the fact that while "The Darl" God, his parents must have hated him) et al spew FUD like an angry volcano, IBM has more or less been quietly operating in the background, most likely when the time is right the IBM suits will calmly pop open their identical briefcases and extract the dental drills, pliers, and electrical probes...

    --
    "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
  39. what Groklaw? by Xtifr · · Score: 4, Interesting

    But definitely keep an eye on the Groklaw site.

    I was trying to keep an eye on Groklaw when it suddenly stopped responding, so I figured it was time to head over to slashdot and see what was new. Sure enough, I found this article pointing to the smoking ruins of what used to be an informative site. :)

    I wonder if it's time for OSDL to offer their hosting services to Pamela?

  40. A Theory by Titusdot+Groan · · Score: 4, Interesting
    I haven't seen this theory before but I don't read ever article posted on this topic :-)

    I think what happened is this:

    1. Some bright intern in SCO legal came across the IBM contract and said "Ah ha!, I bet IBM forgot about this clause."
    2. Some old timer in Legal says, "Hey, we have a bunch of code in escrow from the MERCED, I bet those IBM dummies put some of it into Linux"
    3. Some technical manager is asked to check to see if there is any code in both MERCED and in Linux. Answers "Yes" because he's a climber or is too stupid to know what is or isn't actionable.
    4. SCO launches it's lawsuit.
    5. SCO's real lawyers get the evidence.
    6. Boies, and by deduction everybody else, finds out IBM never forgets when it comes to IP. Never. There is nothing actionable in MERCED that made it into Linux or there isn't enough to make a real lawsuit out of it.
    7. SCO can't find evidence in the source they have so they start requesting source that may have actionable items.
    8. Boies finds out that IBM's lawyers are on to this when they demand real evidence before turning over anything.
    9. The tap dancing begins ...

    Now things are going to get nasty for SCO. What I'm surprised about is how people keep getting surprised by IBM's "Ninja Lawyers" and how tight their IP controls are. It's a long running industry gag.

  41. Santa Claus, the Easter Bunny, and the SCO... by Jahat · · Score: 4, Funny

    evidence walk into a bar....

    --
    Sola Scriptura Sola Fide Sola Gratia Sola Christus
  42. Article is GROSSLY misleading by solman · · Score: 4, Insightful

    SCO has claimed (under penalty of perjury) that they DID produce answers to ALL of IBMs interogatories (questions) before the deadline.

    This includes an answer to IBM's request that they identify (with specificity) all rights that they claim to the Linux operating system.

    We haven't seen this answer (yet). IBM will presumably claim that SCO has NOT answered its questions on January 23rd. But the title of the article is false. SCO _HAS_ produced evidence. The only question is whether or not that evidence is meaningful.

  43. WTF? by C_Kode · · Score: 4, Insightful

    14. I have been informed by SCO's engineers and consultants that since the only version of AIX source code that was available for comparison purposes is several years old, and predates most of IBM's contributions to Linux, it was not possible to directly compare IBM's contributions to Linux with the most likely source of those contributions, namely the missing versions of AIX (including the most recent versions).

    15. Further, we have only one CD of Dynix/ptx source code that was produced by IBM, and this CD only contains a limited history of Dynix/ptx releases. It was therefore not possible to directly compare IBM's contributions to Linux with another likely source of those contributions, namely the missing versions of Dynix/ptx.


    They said they HAVE the proof and you needed to sign an NDA to see it. Yet no all the sudden they don't have all the information required to FIND the evidence they need. So, all these claims are just speculation now? Well, if I can sue for 3 billion off speculation, someones poor multi-billion dollar company is in alot of trouble. Hmmm, I wonder how the judge will see this. What they claim to have had, and what they have are two different things. They have nothing and just admited to it.

  44. SCO wants AIX and Dynix/ptx source code first by Skapare · · Score: 4, Interesting

    SCO claims that their contract with IBM gives SCO all rights to any improvements to these Unix licensed products. In a way, that's kind of like GPL, except for corporate greed, although it seems that it did not provide for any means for SCO to actually get that source code they claim to own. SCO believes that IBM did develop improvements for AIX and/or Dynix/ptx (I presume the original Sequent license for Dynix had a similar provision), and that IBM also contributed those improvements to Linux. SCO thus believes that code they own is in Linux, but cannot positively identify it because they don't have the AIX and Dynix/ptx code to cross check with. Apparently SCO would assert that any code found in AIX or Dynix/ptx is either code originally licensed, or code that was added later by IBM and still covered under the license agreement.

    The clause that gives SCO ownership of improvements to AIX and Dynix/ptx is itself suspect. If there is no provision for transferring that code to SCO, then how is such a clause to have any meaning. And how can it be determined if any improvements were developed by IBM or simply acquired by IBM under other licensing (including GPL) and integrated? If I had sold a piece of code to IBM that would improve AIX and/or Dynix/ptx, a contract between SCO and IBM cannot take ownership of the rights to that code away from me (and I have no contract with SCO). It would not be any different if IBM did this with GPL code. Nor would it make any difference if IBM did this with BSD code. And it wouldn't even make any difference with public domain code (since the public by definition has all rights to use it, so any ownership is moot in that case).

    Suppose there is some common code in both Linux and AIX. SCO might well assert ownership of that code. But what if the code was originally in Linux and subsequently put in AIX (if it is GPL that might be a problem, but suppose it is a public domain, or BSD licensed piece of code). What if the code was in another free licensed OS like FreeBSD, and subsequently put in both Linux and AIX (in either order of time). Or it could be public domain code. SCO won't have any ownership rights to that code (although they could likely have usage right like anyone else).

    SCO will have to do more than merely show that some code is in both Linux and AIX. They will have to prove that IBM developed the code and put it in AIX first, before putting it in Linux. If IBM put the code in Linux first, even under a GPL license, as original owner they also have the right to put it in another system under another license ... and more importantly, cannot subsequently withdraw the rights already granted under the first contribution. So if they put code in Linux under GPL, then put it in AIX under SCO's assertion of ownership rights through the Unix license (which is in dispute), IBM would not be obligated to make AIX open under GPL (since it is not putting it as GPL'd code in AIX). And since the rights under GPL are already released, even if SCO prevails to own the code because IBM developed it, it has no means to withdraw the rights already released under GPL. What SCO would have to prove is that the development was done at IBM, under IBM ownership, for AIX and/or Dynix/ptx, now subject to the disputed license, then donated to Linux under GPL. Just looking at the AIX and Dynix/ptx code isn't going to show that.

    Suppose the worst happens and SCO prevails and the courts believe that certain (at that point identified in court) pieces of code are owned by SCO and their unlicensed distribution and use infringes on SCO's intellectual property. Linux can deal with this very effectively by simply releasing a new version (wanna place bets on how quickly that will happen) without any of that code from IBM. SCO's current case is against IBM, not against Linux. So even if SCO were to prevail, their recovery under that case is only against IBM. There will be two areas of infringement in Linux to consider: the past and the future.

    --
    now we need to go OSS in diesel cars