Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Businesses Government Operating Systems Software The Courts Unix Linux News

SCO Says Email Is Inaccurate 326

daria42 writes "The SCO Group has slammed as 'inaccurate' suggestions that an e-mail from one of its own engineers showed Linux did not contain copyright Unix code, and even forwarded its own historical memo to journalists in an attempt to discredit the e-mail published on Groklaw." From the article: "This memo shows that Mr. Davidson's e-mail is referring to an investigation limited to literal copying, which is not the standard for copyright violations, and which can be avoided by deliberate obfuscation, as the memo itself points out..." We reported on the email yesterday.
This discussion has been archived. No new comments can be posted.

SCO Says Email Is Inaccurate

Comments Filter:
  • Denial. Brilliant! (Score:5, Insightful)

    by suso ( 153703 ) * on Friday July 15, 2005 @11:32AM (#13074190) Journal
    Well of course they would say that. I mean, given their history, is there any other choice they would have for how to respond to this.

    Corporate America feels like a childish game of "You go home.... no you go home..... No you go home.... No"
    • by CaptainZapp ( 182233 ) * on Friday July 15, 2005 @11:54AM (#13074461) Homepage
      Corporate America feels like a childish game of "You go home.... no you go home..... No you go home.... No"

      Actually it reminds me more of the small, obnoxious kid at the sandbox, which sticks his fingers into his ears and yells I CAN'T HEAR YOU! I CAN'T HEAR YOU! on the top of his lungs.

      What a sorry bunch of wankers...

      • by Winkhorst ( 743546 ) on Friday July 15, 2005 @12:34PM (#13074921)
        Actually, my mother used to do that, but not in a sandbox, fortunately.

        NEWSFLASH: SCO today denied reports that they think the world is flat. In a statement issued by CEO Daryl Whats-his-face, the company suggested that they had only meant to say that there were certain parts of it that appeared to be flat. "This is fully within the parameters of linguistic theory," said Daryl. "We never meant to imply that it's ALL flat." Daryl refused to elaborate on which areas of the world he thought "looked" flat.
      • by superyanthrax ( 835242 ) on Friday July 15, 2005 @01:11PM (#13075344)
        Unfortunately the "sorry bunch of wankers" is having a negative effect on Linux's reputation. Founded or not, their claims just add to the FUD that Microsoft puts out to combat Linux's spread, and it's having a significant effect.
        • by Rimbo ( 139781 ) <rimbosity AT sbcglobal DOT net> on Friday July 15, 2005 @03:35PM (#13076867) Homepage Journal
          Unfortunately the "sorry bunch of wankers" is having a negative effect on Linux's reputation. Founded or not, their claims just add to the FUD that Microsoft puts out to combat Linux's spread, and it's having a significant effect.

          It did for the first 6 months of the case. But recent studies have shown that pretty much nobody cares about it any more; if anything, it's accelerated adoption, because the continuing lack of evidence from SCO is making Linux look more stable, not less.


    • He is well beyond the point where that sort of statement could help his standing / hurt Linux in any way, even in the press. There is an old rule that you cant really trust a controversial news item until it has been honoured with a dementi. Ok, confirmation.
      However, I wonder if that email might lead to another front in the SCO litigation labyrinth since it might be used to argue that SCOs going to court was frivoluos from the very beginning. /. crowd said so all the time but convincing yourself is still an
    • by Rei ( 128717 ) on Friday July 15, 2005 @12:09PM (#13074634) Homepage
      feels like a childish game

      SCO: "NO! It's MY fingerpainting, and he took it from me! Mine, mine, mine, mine!!!"

      Parent: "Honey, it's not your fingerpainting, I saw him make it the other day. It doesn't even look like yours."

      SCO: (hands over ears) "La La LA LA LA, I can't hear you, La La LA LA LA!!!!"
    • SCO has been backpedalling for so long that they've added an extra gear to the mix. This allows them to claim that they're pedalling forward while they're going backwards at full speed.

      Some people might call this 'reverse gear', but they've given it a new name and managed to patent it as a business method.

  • by nokilli ( 759129 ) on Friday July 15, 2005 @11:32AM (#13074192)
    From cnet we have this story [com.com]:
    Lines from Unix's source code have been copied into the heart of Linux, sometimes exactly and sometimes in a modified form designed to disguise their origin, according to SCO Group Chief Executive Darl McBride.
    ...and within which Darl McBride is quoted as saying:
    "We're finding...cases where there is line-by-line code in the Linux kernel that is matching up to our UnixWare code."
    So sell your bullshit somewhere else, Darl. We're all stocked up here.
    --
    Why didn't you know? [tinyurl.com]
    • by Patrik_AKA_RedX ( 624423 ) on Friday July 15, 2005 @11:46AM (#13074368) Journal
      <blockquote>"We're finding...cases where there is line-by-line code in the Linux kernel that is matching up to our UnixWare code."</blockquote>

      From a good source I know Linux does indeed contain lines that are exactly the same as in UnixWare Code.

      e.g.:

      for (int i = 0; i < MAX_INT; i++)

      while (!done)

      ...

      There are many more to find. SCO has even reason to believe many more companies has copied these exact same code fragments!
      • From a good source I know Linux does indeed contain lines that are exactly the same as in UnixWare Code.

        e.g.:
        for (int i = 0; i < MAX_INT; i++)

        Very unlikely that this kind code is on Linux (kernel), because that is not C.

        (It looks like C++ code. )

        • looks more like C# or maybe Java...?

          nothing wrong with that syntax in any C-based language (including C) other than the fact that there's no end to the statement.
          for (int i = 0; i < MAX_INT; i++)
          i--;
          Now that represents the SCO lawsuit better.
          • And the fact that it won't compile :-)

            "for (int i"? C won't let you declare a variable in that context. D'uh!
            • "for (int i"? C won't let you declare a variable in that context. D'uh!

              Really? Let's try it!

              haeleth@cynewulf ~
              $ cat > test.c
              int main (void)
              {
              for (int i = 0; i < 10; ++i) {
              // do nothing
              }
              return 0;
              }

              haeleth@cynewulf ~
              $ gcc -Wall -pedantic -std=c99 test.c

              haeleth@cynewulf ~
              $

              Hmm, it compiled. And note the conspicuous absence of any errors or warnings whatsoever, which indicate that the code in question is 100% strict valid C in accordance with the current C standard (ISO C99).

          • Yeah. Everybody knows that 'i' was supposed to be unsigned.

      • by Rei ( 128717 ) on Friday July 15, 2005 @12:15PM (#13074701) Homepage
        You wouldn't believe how many times they copied lines. They even used similar variables and function names, containing words like SCSI, interrupt, and other such terms.

        Now, if we do a statistical analysis, given 26 lower case characters, 26 upper case characters, 10 numbers, and the '_', along with 9 letters in 'interrupt', we come to the conclusion that the odds of repeating that exact term just *once* (let alone the many times like Linux does) are about 16,000,000,000,000,000,000 to 1. Linux has, quite obviously, been seriously ripping off UnixWare.
      • ROTFLMAO !!

        Someone tosses in a "one liner" and the /. crowd goes nut with the correction and clarifications.

        Its like the uber-geek grammar police for code -and they travel in packs around here.
    • by bigjocker ( 113512 ) * on Friday July 15, 2005 @11:50AM (#13074424) Homepage
      Not only that, but they are claiming that a 1999 investigation proves wrong the one performed on 2002.

      Also, later on they claim that 'SCO also pointed out its legal wrangling with IBM dealt with more recent versions of the Linux code than were mentioned in the memo'. Are they saying the more recent version was available on 1999, but not in 2002?
      • Obviously people went through optimizing the Linux kernel by tearing large chunks of well tested and integrated code and replacing them with aritrary blocks of SCOs code.
      • by burnin1965 ( 535071 ) on Friday July 15, 2005 @02:46PM (#13076358) Homepage
        The actual 1999 "preliminary conclusion" from Swartz is very critical of linux and makes some very damning statements, i.e.
        "many portions of Linux were clearly written with access to a copy of Unix sources."
        "they started with a source file which apparently came from Unix and is thus the property of SCO."

        So Swartz is telling SCO management what they want to hear, and this is also what they expect everyone to take from this 1999 letter. That is that linux infringes on SCO's copyrights.

        Now what SCO likely is hopeful nobody reads from the 1999 letter are the following statements from Swartz after stating his claims:
        "One of the questions which remains to be answered is what is the history of the identical code. It is possible that some of the code came from Berkeley or other third party."
        And most importantly:
        "I am awaiting an analysis from Mike Davidson on some of these issues, since he has a better feel for the history of much of this code."
        So the claims Swartz makes in this "preliminary conclusion" seem rather harsh considering he doesn't know the history of the code which he finds suspect.

        And then the clincher. When Mike Davidson comes back with the analysis Swartz is waiting on we get from Mike's follow up email in 2002:
        "We had found absolutely *nothing*"
        "invariably it turned out that the common code was something that both we (SCO) and the Linux community had obtained (legitimately) from some third party."
        So it becomes obvious from the 1999 letter and the 2002 email that while Swartz did find similar code between linux and SCO's Unix in the end when the findings were presented to the SCO Unix source code expert it was discovered that none of the similar code belonged to SCO and there were no copyright infringements in linux.

        I must say, it was nice reading the actual emails instead of listening to the obfuscation of facts from the lawyers and the media.

        burnin
  • by NastyNate ( 398542 ) on Friday July 15, 2005 @11:33AM (#13074200)
    No Copyright violations for you to see here. Please move along.
  • by It doesn't come easy ( 695416 ) * on Friday July 15, 2005 @11:34AM (#13074211) Journal
    Everything out of SCO has been inaccurate up to this point...
    • by superpulpsicle ( 533373 ) on Friday July 15, 2005 @11:49AM (#13074410)
      SCO engineer: I compared the codes they are different.

      SCO lawyer: You mean they are the same.

      SCO engineer: No, I mean they are different.

      SCO lawyer: You mean they are the same.

      (Repeat the above 4000 times)

      SCO engineer: Yes... they are the same master!

      • by Tackhead ( 54550 ) on Friday July 15, 2005 @12:01PM (#13074547)
        > SCO engineer: I compared the codes they are different.
        > SCO lawyer: You mean they are the same.
        > SCO engineer: No, I mean they are different.
        > SCO lawyer: You mean they are the same.
        > (Repeat the above 4000 times)
        > SCO engineer: Yes... they are the same master!

        Linus: Different.
        Darl: Same.
        Linus: Different.
        Darl: Same!
        Linus: Same!
        Darl: Different!
        Judge: *slams gavel on Darl's beak* Case dismissed!

        Darl: [twisting his beak from his jaw to the front of his face] Let's run through that again.

        Linus: Same.
        Darl: DIFFERENT! SUE THE TUX! SUE THE TUX!
        Judge: *slams gavel on Darl's beak again*

        Darl: [picking his beak off the floor] You're... dethpicable.

  • Deny mode. (Score:5, Insightful)

    by theantipop ( 803016 ) on Friday July 15, 2005 @11:34AM (#13074216)
    Well of course they're going to say that. Did anyone expect them to say "Ah, yea you got us. We were bullshitting this whole time."?
  • This is just them desperately trying to hold onto their useless lawsuits as long as possible. I'm sure it is not just one engineer, but rather nearly every employee who knows attacking linux is nothing more than a money grab.
  • Avoiding Jail (Score:5, Interesting)

    by drooling-dog ( 189103 ) on Friday July 15, 2005 @11:36AM (#13074235)
    Anybody else getting the feeling that these guys are just trying to stay out of jail now?
  • by gsfprez ( 27403 ) * on Friday July 15, 2005 @11:37AM (#13074248)
    how the fcsk can it be than a 1999 investigation's initial findings, the Swartz investigation, show up "possible problems" and then in 2002, with Reg and Co examining the output of the 1999 investigation in 2002 and deeming that all the "problems" found in 1999 were actually NOT problems...such as legal use of BSD code, etc...

    but the initial 1999 look trumps the more thorough 200*BANG*

    my mind just exploded.

    i hate this case.
  • Scrambling... (Score:5, Interesting)

    by Phs2501 ( 559902 ) on Friday July 15, 2005 @11:38AM (#13074259)
    I love the sweet smell of desperation. From the letter in question (strong tag mine):
    Bob worked on the project for (I think) 4 to 6 months during which time he looked at the Linux kernel, and a large number of libraries and utilities and compared them with several different vesrions of AT&T UNIX source code. (Most of this work was automated using tools which were designed to to fuzzy matching and ignore trivial differences in formatting and spelling)

    At the end, we had found absolutely *nothing*. ie no evidence of any copyright infringement whatsoever.

  • Example (Score:2, Funny)

    by Anonymous Coward
    Here is an example of code that was STOLEN directly from the Unix code...

    int var1;

    And here's one they blatantly obfuscated:

    Original:
    int var1;
    var1 = 0;

    Obfuscated:
    int var_1 = 0;

    HOW DARE THEY!
  • Have your cake (Score:5, Informative)

    by dysk ( 621566 ) on Friday July 15, 2005 @11:41AM (#13074300)
    From http://www.groklaw.net/article.php?story=200310102 23050711 [groklaw.net]

    Question: Isn't it possible that someone was just inspired by work they'd done for other companies? Isn't that reasonable?

    Darl(21:50): It's reasonable, except when the comment codes are the same, the humor lines in the comment code are the same, and the typos in the comment code are the same, then you start getting beyond... Ya know, it was kind of like, I learned this one day at school ... It becomes more of the... Those, to me, are really the DNA of the code here.

    • Bible verse (Score:2, Funny)

      by Anonymous Coward
      Darl(21:50): It's reasonable, except when the comment codes are the same, the humor lines in the comment code are the same, and the typos in the comment code are the same, then you start getting beyond...

      What the? Is that a Bible Verse? John (3:16), Darl (21:50).
  • Is (Score:4, Funny)

    by paimin ( 656338 ) on Friday July 15, 2005 @11:41AM (#13074303)
    It depends on what your definition of "is" is.
  • But... (Score:5, Informative)

    by venicebeach ( 702856 ) on Friday July 15, 2005 @11:41AM (#13074310) Homepage Journal
    The email itself says that the investigation looked for more than literal copying. From the email:

    Bob worked on the project for (I think) 4 to 6 months during which time he looked at the Linux kernel, and a large number of libraries and utilities and compared them with several different vesrions of AT&T UNIX source code. (Most of this work was automated using tools which were designed to to fuzzy matching and ignore trivial differences in formatting and spelling)
  • by crimethinker ( 721591 ) on Friday July 15, 2005 @11:41AM (#13074316)
    So if Darl says that the 2002 memo only cleared linux of "literal" copying and didn't find deliberate obfuscation, how does he justify the "entire sections of code verbatim" remarks he made to the press?

    I smell a shareholder lawsuit, an SEC investigation, and hopefully, a Sarbanes-Oxley smackdown of such grand proportions as to make Bernie Ebbers look like a slap on the wrist.

    -paul

    • by CyricZ ( 887944 ) on Friday July 15, 2005 @11:51AM (#13074440)
      Bernie Ebbers orchestrated an $11 billion fraud. While McBride has bumfucked some people over, that is for sure, it is nowhere near the scale of what Ebbers had done. What makes you think that McBride will receive a punishment that will make what Ebbers got "look like a slap on the wrist"?

      • Bernie Ebbers orchestrated an $11 billion fraud. While McBride has bumfucked some people over, that is for sure, it is nowhere near the scale of what Ebbers had done. What makes you think that McBride will receive a punishment that will make what Ebbers got "look like a slap on the wrist"?

        You're right. It probably won't. But I think that sentiment is rooted in the hope that the courts will rule this was a completely frivolous action and therefore deserving of a decent knuckle-rap.

        They are, after all

      • To be honest, the scale of the deception shouldn't always be the guide, but the nature of the deception. From what I gather, internal bookkeeping was almost an accepted practice by many of these companies, but bring a lawsuite against not one, not two but three companies in an attempt to extort buyout cash is not only a breach of their responsibility to the share holders, but an outright misuse of the judicial system. That, IMHO, is the biggest thing they did and for that they should be slapped from here
    • Mod parent up.

      SCO's damage control is getting sloppy. The "literal copying" accusations were their biggest media grabs, and per this email, SCO was knowingly misleading their shareholders, the government and the media.

      The only "delibirate obfuscation" can be found in SCO's pathetic and hysterical finger pointing, the trails of which form not only a rat's nest of weak arguments but - thanks to this email - apparently also the knot in the noose around their necks.

  • by It doesn't come easy ( 695416 ) * on Friday July 15, 2005 @11:43AM (#13074326) Journal
    However, SCO said in a statement this afternoon, "it would simply be inaccurate - and misleading -- to use Mr Davidson's e-mail to suggest that SCO's internal investigation revealed no problems."

    Problem number 1: Linux doesn't contain any of SCO's intellectual property.
  • Go to the source (Score:5, Insightful)

    by wfs2mail.com ( 794623 ) on Friday July 15, 2005 @11:43AM (#13074328)
    Does anyone know who Mr. Davidson is? Has anyone tried contacting him re: this email?
  • by CyricZ ( 887944 ) on Friday July 15, 2005 @11:44AM (#13074336)
    I still find it very interesting that the SCO developer in question sent the email from a computer running Windows 98.

    It contains the email header "X-Mailer: Mozilla 4.6 [en] (Win98; I)".

    Now, it would make sense for secretaries and perhaps other execs to be using Windows 98, but not one of their UNIX and Linux developers. Even if he wasn't using UnixWare or OpenServer as his workstation OS, he should very well have been using OpenLinux.

    And remember, the email was sent in 2002. This is well after the release of Windows 2000. Even the use of Windows 2000 or Windows NT would be somewhat understandable. But Windows 98? That strikes me as very unsual.

  • by kawika ( 87069 ) on Friday July 15, 2005 @11:44AM (#13074346)
    Yes, SCO has found cases where their copyrighted code was stolen and then cleverly obfuscated by completely changing the variable names, comments, data structures and algorithms! But clearly it must have been stolen since it performs a similar function.
  • The SCO gang should become history books writers. They would change the way we look at the history of the world. I mean Blake Stowell take on modern history would be likely to be stating something like 'Our research have found this statement from 1929 from Adolf Hitler stating that he liked Jews, this earlier statement of course invalidates everything that happened afterwards and shows that Hitler have been deeply misrepresented as a proponent for anti-semitism.'
  • Liar Liar (Score:4, Funny)

    by UnrefinedLayman ( 185512 ) on Friday July 15, 2005 @11:50AM (#13074415)

    Haven't I seen this before?

    "Your honor, I object!"

    "And why is that, Mr. Reede?"

    "Because it's devastating to my case!"

    "Overruled."

    "Good call!"

    • by Anonymous Coward
      Lt. Weinberg: "'I strenuously object?' Is that how it's done? Hm? 'Objection, your Honor.' 'Overruled.' 'No, no. I STRENUOUSLY object.' 'Oh. You strenuously object. Then I'll take some time and reconsider.'"
  • by Anonymous Coward on Friday July 15, 2005 @11:51AM (#13074434)
    Current events:
    • SCOvIBM: In the wake of the recent opinion [groklaw.net] issued by Judge Kimball, fact discovery will continue until 27 Jan 2006, and the parties must disclose with specificity all "allegedly infringing materials" by 22 Dec 2005. Redacted and unsealed motions are dribbling out. The parties seem to be still consulting [groklaw.net] with each other on the privilege log issue. Finally, a fully briefed, completely sealed discovery motion [groklaw.net] awaits a ruling, though no hearing date is yet set.

    • SCOvNovell: Judge Kimball has denied Novell's motion to dismiss. The likely next step here is for Novell to file an answer to SCO's complaint.

    • RedHatvSCO: This case remains stayed. However, Judge Robinson indicated that if "it would no longer be an inefficient use of judicial resources" or "there is evidence that SCO has misrepresented the issues," Red Hat can refile their motion for reconsideration to lift the stay. The parties are instructed to update the court every 90 days on related actions in which SCO is involved. The next update is due approximately 28 Sept 2005.

    • SCOvAutoZone: Judge Jones stayed this case "pending further order of the court" and the parties are instructed to update the court every 90 days on the other related actions in which SCO is involved. The next update is expected around 17 July 2005.

    Pending/Recently decided motions:

    • SCOvIBM:
      • SCO's Renewed Motion to Compel Discovery - fully briefed, awaiting hearing date.
      • [Motion] [groklaw.net] [Memo - sealed] [Opposition - sealed] [Reply - sealed]

    SCOvNovell:

    RedHatvSCO:

    SCOvAutoZone:

    Please note that I've started construction of a motio [blogspot.com]

  • by RealProgrammer ( 723725 ) on Friday July 15, 2005 @11:53AM (#13074455) Homepage Journal
    I'm not a GNU fanboy, but the GPL works wonderfully.

    You see, SCO shipped Linux for years. They did so, knowingly, under the GPL. The GPL was their license.

    They claimed that they stopped shipping Linux as soon as they could when they realized that IBM was "dumping UNIX code into Linux". That's hogwash, but that's not my point.

    The point is that now, when they claim there were pre-IBM copyright violations, they are caught by the GPL. They shipped all that code included in Linux and other supporting programs under the GPL.

    If they believed there was SCO code hidden in Linux, shipping under the GPL means they approved of it.

  • by Anonymous Coward
    The SCO IP website has made a Swartz memo available here: Which seems to be entirely different and gives concrete information on similarities and copied code. I haven't verified the conclusions but this is what SCO is now making public to confuse people.
  • by Peter Simpson ( 112887 ) on Friday July 15, 2005 @11:56AM (#13074485)
    Your "denial in the face of overwhelming evidence to the contratry" skills are needed in Utah!
  • OMGWTFBBQ (Score:5, Interesting)

    by aws4y ( 648874 ) on Friday July 15, 2005 @11:57AM (#13074493) Homepage Journal
    I just read the Fscking email and it says the opposite of what Stowell said. The email states directly that this entire scheme was concoted because executives cannot understand that simpling because two things work the same way it dosent mean that one thing is a copy of the other. This just makes them look more guilty of sock manipulation, this also brings into question there direct statements to the public. If an officer at a corporation lies to the public but didn't know it at the time then he or she made a mistake. If you lie to the public and you know its a lie, then that is fraud.

    this memo clearly shows that SCO executives knew that there was no litteral copying in GNU/Linux, they then went out and made statements that they new were demonstrably false, i.e. Daryl's Line by Line copying comment. It is now very clear that SCO executives should at least be charged with fraud.

    • If you lie to the public and you know its a lie, then that is fraud. What if you lie to the public and you can tell that it is a lie because you're fucking nuts? I smell an insanity defense in the works for Darl... at least, that is the only rational explanation I can come up with to explain his public statements!
  • by Anonymous Coward on Friday July 15, 2005 @12:01PM (#13074538)
    If SCO does end up prevailing at all in this circus, then I predict that someday musical instument makers, like say for example, Stienway Pianos, will claim that because you used one of their pianos to compose a song, then that song is automatically a "derivative work" of their I.P. and therefore you must pay license royalties back to them. Ditto for public performances played on the instruments. A portion of each concert ticket sold must be paid back to them, and free public performances would be outlawed because that would be "stealing potential revenue" from them.

    Someday, you will have to agree to a usage rights control contract for everything you buy.

    Somebody will patent some kind of registration system to track all kinds of usages of all these products and you're be required to be a member of that before you'll even be able permitted to purchase anything at all, and you'll actually not be purchaing anything, but rather leasing the temporary usage rights for a short term.
  • Considering the earlier story, I would have thought that they would have just claimed that this email was spam.

    They could easily get rid of 90% of incriminating emails that way.

    "No your honour, that isn't evidence of us being lying weasels, it is spam. By the way, do you want to En14rg3 yur p3ni5?"

  • They looked.

    They found nothing.

    Nothing to see here except more lies. Move along.
  • How many businesses have been harmed by SCO's miSCOnduct in the courts that diSCOuraged many potential customers from buying Linux based solutions? How many lawsuits could these businesses file to try to recover losses from this fiaSCO? What other smoking guns would these new suits diSCOver?

    I, for one, would just like to be the one to eSCOrt Darl and the other SCOundrels and SCOfflaws to jail. But I'll just have to work, like everyone else, to just recover the SCOrched Linux landscape.

  • http://finance.yahoo.com/q/bc?s=SCOX&t=5d&l=on&z= m &q=l&c= [yahoo.com]

    Hot on the heels of yesterday's revelation that SCO's claims were outright lies, their stock started the day with a nose-dive to under 3.80

    But since then, Microsoft (under cover of disguise) has poured more money into SCO's stock to give the appearance that the truth coming to light did not damage SCO.

    I find that really funny, personally.

    I hope Microsoft enjoys losing face and being laughed at like this.

    It'll be REALLY funn
  • I thought that SCO was now claiming that it owned JFS and some other code that IBM wrote and put into AIX? Didn't SCO give up on the claim that UNIX code made it into Linux? Or have they forget what they have and have not said?
  • by Solr_Flare ( 844465 ) on Friday July 15, 2005 @01:34PM (#13075596)
    Sue SCO for emotional distress due to constantly laughing his ass off at them.

    He'd have a better chance at winning that too than SCO ever will with their case.
  • by mcc ( 14761 ) <amcclure@purdue.edu> on Friday July 15, 2005 @02:04PM (#13075935) Homepage
    Groklaw has covered this 1999 email, but it's in an update to an earlier story [groklaw.net] rather than a story by itself. I thought they had a pretty good take on it and I wanted to quote something here.

    Here's what IBM apparently had to say when the 1999 email first surfaced in court:
    "SCO seeks to explain away the e-mail to which I referred [slashdot.org] by reference to a 1999 memorandum. Now, Mr. Hatch says that he understands that we have this memorandum. We have it because it was given to us hours before today's hearing. We got it this morning. It should have been produced a long time ago, but IBM is supposedly a party in breach of its discovery obligations.

    Your Honor, the memo was dated five years ago. It was written three years before the e-mail which I have showed to Your Honor. It is a draft. It says on its face that it is provided, quote, 'subject to the further analysis of Mr. Davidson'. That's on page 5 of the fax sent to us this morning by Mr. Hatch. On the last page of the document, page 6 of the fax, he says, 'I'm awaiting analysis from Mike Davidson on some of these issues since he has a better feel for the history of much of this company.'

    "Well, Your Honor, Mr. Davidson weighed in, in the e-mail we provided to Your Honor. In that e-mail, he makes abundantly clear in the last two paragraphs what he said when he weighed in.
  • by UnknowingFool ( 672806 ) on Friday July 15, 2005 @02:27PM (#13076169)
    Somebody once told me that it's easier to tell the truth because you won't have to remember what you lied about. SCO might want to check which version of truth they want to use this week.

    "This memo shows that Mr. Davidson's e-mail is referring to an investigation limited to literal copying, which is not the standard for copyright violations, and which can be avoided by deliberate obfuscation, as the memo itself points out," the company continued. SCO also pointed out its legal wrangling with IBM dealt with more recent versions of the Linux code than were mentioned in the memo.

    Forgetting the fact that Darl has publicly announced many times that literal copying is in Linux, SCO's current statement is still contradicted plainly in the email:

    Bob worked on the project for (I think) 4 to 6 months during which time he looked at the Linux kernel, and a large number of libraries and utilities and compared them with several different vesrions of AT&T UNIX source code. (Most of this work was automated using tools which were designed to to fuzzy matching and ignore trivial differences in formatting and spelling)

    Of course SCO will probably now claim that "fuzzy matching" meant comparing furry code or some inane b.s. like that.

To stay youthful, stay useful.

Working...