15 Jul 2005
An internal investigation at SCO in 1999 reported that not a single line of code in the Linux kernel was found that violated SCO's copyright, according to an email datad 13 August 2002 which was obtained by legal website Groklaw.
Bob Schwartz, an outside consultant, spent between four and six months comparing Linux with the so-called AT&T Unix code.
Further reading
"SCO was sure that it was going to find evidence of copyright violations," a SCO employee wrote in an internal email. "At the end, we had found absolutely nothing: no evidence of any copyright infringement whatsoever."
In cases where there was an overlap between SCO's Unix code and Linux, both software suites obtained the code legitimately from some third party, the email stated.
The message was addressed to SCO senior vice president Reg Broughton who forwarded it to chief executive Darl McBride.
SCO made a statement in response to the posting: "This memo shows that Mr Davidson's email 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.
"Even more importantly, this memo shows that there are problems with Linux. It also notes that additional investigation is required to locate all the problems, which SCO has been continuing in discovery in the IBM and Autozone cases.
"Thus, even aside from the fact that SCO's central contract claims in the IBM litigation involve later Linux versions and different conduct, it would simply be inaccurate and misleading to use Mr Davidson's email to suggest that SCO's internal investigation revealed no problems."
SCO filed a lawsuit against IBM in 2003, demanding mor e than $1bn in damages for alleged copyright violations. SCO claims ownership of the so-called AT&T Unix source code and alleges that Linux developers copied parts of the code.
The case has been slowly proceeding through the courts, but SCO has not yet produced any proof of the copyright violations.
Although the email obtained by Groklaw pleads against SCO, it does not suggest that the company has no other evidence that incriminates Linux and IBM. When contacted IBM declined to comment.
Latest stories from Open Source
Related articles
Related jobs
Poll
Are you confident that the UK's IT infrastructure is secure from attack in the wake of the Flame malware revelations?
TFL director of Games transport Mark Evers discusses how the public transport network is preparing for this summer's event
Connect with V3.co.uk
The wrong printers, for the wrong tasks on the wrong contracts
Who leads the BI pack and who should we be watching out for?
THIS ROLE IS LOOKING AT IMMEDIATE STARTERS AND WITH MULTI...
Sales Consultant - Data Centre, Colocation, Hosting...
Senior Interaction Designer (User Experience, UCD, Interactive...
Information Architecture / IA / User Experience / UX...
Keep up to date with the latest products, services and technologies from the world's leading IT companies. IThound.com brings you over 2,000 white papers, case studies and analyst reports.
Do you agree?
Not idiots. Just you.
You should post *after* you know the facts of the case at hand, not before. This is about SCO alleging that IBM put proprietary (therefore not reuseable) code into Linux. Since it is a complete lie, they can't find a real instance of this happening. There may be similarities (you can only increment a pointer or clear a buffer so many ways), but that has nothing to do with what you're talking about. The point is that SCO has been saying for years that is has mountains of evidence - millions of lines of code that was directly "line-by-line" copied. This study which was done by someone that they hired said that there was no such thing. They paid someone to find the similarities and he couldn't find any. That is what this article about. The author has the facts together much better than you do. You would be much better off posting your ignorance with the rest of the gibberish on msdn. Someone there might actually believe you know what you're talking about. Using a windows MFC class to create a "Hello World" window doesn't mean that you know about code. Making ignorant posts doesn't mean you know the first thing about this case.
Posted by: Holier than Thou 16 Jul 2005
USL vs BSDI suit proved UNIX not protectable!
I you read the judges words from the USL vs BSDI injunction related ruling (against USL) you will understand that a Judge has already said that AT&T Unix (owned by USL at the time) was not protectable. Read this whole web site and you will see why SCOx has no case: http://cm.bell-labs.com/cm/cs/who/dmr/bsdi/bsdisuit.html "A further consideration is that 32V's overall organization may not even be protectable in the first place". Read the commentary on Groklaw about the "settlement (signed 2/4/1994) between USL and UCB" that pertained to UNIX and points to the fact that USL at the time understood that they did not author or control code much of the code in UNIX. http://www.groklaw.net/article.php?story=20041126130302760 SCOx does not own UNIX (due to the acts and lack of acts of agents of AT&T folks are free to create Operating systems that are like UNIX)! This has been true for a very long time! SCOx just would like to reverse history and rewrite it to their own liking. If they succeed it will mean that all logic is no longer logical...
Posted by: Anonymous Groklaw Reader 16 Jul 2005
A better way to make money
Well it's pretty obvious that SCO thought this would be an easy way to boost revenue: claim ownership of parts of the kernel. Instead of putting their efforts into making revenue by plaeasing customers with quality products. Patent lawsuits are a minefield of nonsense. For instance the Kodak Vs Sun Case a while back. I hope that SCO go bust defeding this giberish.
Posted by: Gerry 16 Jul 2005
idiots
I hate all non windows computers, but i'm smart enough to know, that just about every programs shares 1 line of code, probably hundrededs, get your facts straight, code is resuable, it would be like winning loto if a program didint contain 1 line of code of another
Posted by: dfgdfgf 15 Jul 2005