decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books
Your contributions keep Groklaw going.
To donate to Groklaw 2.0:

Groklaw Gear

Click here to send an email to the editor of this weblog.


To read comments to this article, go here
"maddog" to SCO: "ID Your Code If You Don't Want It in Linux, Because We Certainly Don't Want It" --
Friday, June 27 2003 @ 03:48 PM EDT

"maddog" to SCO: "ID Your Code If You Don't Want It in Linux, Because We Certainly Don't Want It" --
Listen to 2003 Usenix Conference on SCO



There is an MP3 of the June 9-14, 2003 Usenix Conference on SCO available. It makes reference to slides, which you can find here, so you can follow along during the talks by opening two windows or two browsers. The panel includes Chris DiBona, a former Slashdot editor and founder of Damage Studios, Jon "maddog" Hall, President of Linux International, and Don Marti, editor of Linux Journal.

Topics include coverage of the SCO claims, the ex-SCO employee who says the code was put there by his group when they worked on the 2-year UNIX-Linux merge of code, and an idea for examining code using software developed by a university to detect plagiarized code in large software projects which also can be used to keep a history of software contributions and which they are thinking of asking to use to search for older BSD code to see if identical code is also in there prior to System V.

De Bona's read on the SCO claims: "SCO is saying 'Legally we deserve profits.'" Jon "maddog" Hall says that SCO's refusal to tell what the code is makes it impossible to fix the problem. He wishes they would and says, "Take your code, please! We don't want it." They also touch on how clean code practices in proprietary companies as compared with Linux, and all agree that both are vulnerable to problems and each have systems to prevent such problems. Hall and De Bona mention several examples of such incidents that have occured in proprietary software over the years, including the MS SQL Server case, where MS was found guilty of patent violations.

Hall also mentions an OSDL lab in Portland, Oregon, where coders can test code in an environment that can handle large projects. They also have projects, including one to make Linux carrier grade for use in telephone systems. SCO, until recently, he says, was a member and as a result, code could have been passed in either direction in that lab, from SCO to Linux, for example, or each could have gotten it from BSD. The current OSDL page does not list SCO as a sponsor, but the Wayback Machine shows Caldera Systems listed as a sponsor on the same page back on both December 22, 2001 and February 28, 2002.


  View Printable Version


Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )