Slashdot Mirror


SCO Says Email Is Inaccurate

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.

16 of 326 comments (clear)

  1. Nice try, Darl, but... by nokilli · · Score: 5, Informative
    From cnet we have this story:
    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?
  2. Have your cake by dysk · · Score: 5, Informative
    From http://www.groklaw.net/article.php?story=200310102 23050711

    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.

  3. But... by venicebeach · · Score: 4, Informative

    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)

  4. Re:Denial. Brilliant! by eln · · Score: 5, Informative

    Yes, they all lie, and the reason is because it works. Those of us who follow this case, or who take what people in these positions say with a grain of salt and do our own research are not usually fooled by such things, but the majority of people are. Most people are content to trust people in power rather than questioning them.

    It's unfortunate that the idea of questioning powerful people has become taboo in our culture, as it gives those people that much more power to do whatever they please. The only way to keep power in check is for the relatively powerless to continually question it.

  5. Current events, calendar. by Anonymous Coward · · Score: 5, Informative
    Current events:
    • SCOvIBM: In the wake of the recent opinion 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 with each other on the privilege log issue. Finally, a fully briefed, completely sealed discovery motion 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] [Memo - sealed] [Opposition - sealed] [Reply - sealed]

    SCOvNovell:

    RedHatvSCO:

    SCOvAutoZone:

    Please note that I've started construction of a motio

  6. Re:A SCO developer running Windows 98? by ratboy666 · · Score: 4, Informative

    Why is that strange?

    I am a Solaris/AIX/HPUX/Linux developer, and I have two (2) machines at home running Windows 98SE.

    Works fine, never had the need to upgrade or change it out.

    So, if you get an email from me, it will either be from one of a myriad of Unix boxes, or Windows 98.

    Ratboy

    --
    Just another "Cubible(sic) Joe" 2 17 3061
  7. Re:Avoiding Jail by drakaan · · Score: 2, Informative
    You know what, even *that* statement from them is bullshit. The e-mail itself says (cut-n-paste from Groklaw):

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

    Correct me if I'm wrong, but, fuzzy matching and ignoring trivial differences, etc doesn't sound like "an investigation limited to literal copying".

    Of course, they said it in the press, not in court, so they won't get in legal trouble for it.

    --
    "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
  8. Re:Tricky Linux programmers by Anonymous Coward · · Score: 1, Informative


    Wanna proof? Check this. The ascii sum of all characters in all Linux' source code, modulo 666 is equal to 666! Works for every version ever released!

    Go back to math class. A number mod 666 can never equal 666

  9. Re:A SCO developer running Windows 98? by CyricZ · · Score: 2, Informative

    No, the email in question was clearly from Michael Davidson, and not from some consultant. Below are the headers, so you can see for yourself.

    Date: Tue, 13 Aug 2002 13:26:51 -0700
    From: Michael Davidson
    Organization: Caldera International
    X-Mailer: Mozilla 4.6 [en] (Win98; I)
    X-Accept-Language: en
    To: Reg Broughton
    Subject: Re: Patents and IP Investigation
    [1]

    Again, Mr. Davidson was a SCO engineer, not a consultant.

    In the Aug. 13, 2002, e-mail, engineer Michael Davidson said "At the end, we had found absolutely nothing ie (sic) no evidence of any copyright infringement whatsoever."
    [2]

    References:
    [1] http://www.groklaw.net/article.php?story=200507141 44923365
    [2] http://news.zdnet.com/2100-3513_22-5789132.html

    --
    Cyric Zndovzny at your service.
  10. Re:Denial. Brilliant! by Master+of+Transhuman · · Score: 2, Informative

    Mod: -5, Bush troll.

    Additional Mod: -3 Probably Microsoft troll.

    --
    Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  11. Re:I'm getting a bit bored with this by DrJimbo · · Score: 2, Informative
    91degrees wrote:
    They [SCO] must have at least some sort of case for the trial to have got this far.

    Sorry, that's incorrect. But, you do get this watch and a year's supply of turtle wax.

    I am not claiming that Groklaw is impartial but they do have a lot of facts there that you can go check. You might be interested in reading Judge Kimball ruling (from February 2005) where he expressed astonishment that SCO has not yet presented one shred of evidence that IBM has done anything wrong.

    --
    We don't see the world as it is, we see it as we are.
    -- Anais Nin
  12. Re:Avoiding Jail by arkanes · · Score: 3, Informative
    The PDF of the memo, which spells out the methodology in some detail, specifically says that he's looking for exact and near-exact textual matches. It's possible that the the email author mis-remembered, or that further studies/analysis were done between the memo and the email (3 years, remember), but Stowells statement is not an out and out lie (he's characterising the memo, not the email).

    Which is not to say that the memo is worth a shit anyway, since whatever the results were they were discared in later analysis, as the email demonstrates, and in any case analysis by far more qualified people (like Brian Khernigan) has come up empty as well.

  13. Groklaw's take on the 1999 memo. by mcc · · Score: 5, Informative
    Groklaw has covered this 1999 email, but it's in an update to an earlier story 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 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.
  14. SCO doesn't even know how to lie properly by UnknowingFool · · Score: 4, Informative
    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.

    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  15. SCO hopes nobody reads... by burnin1965 · · Score: 3, Informative
    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
  16. Re:Not surprised... by bleak+sky · · Score: 2, Informative

    Rabbit season!
    Duck season!

    I had almost forgotten that episode. Best ever...