Slashdot Mirror
USENIX Panel On SCO Lawsuit Now Available
porkrind writes "No Starch Press and The USENIX Association co-sponsored a discussion on the SCO vs. IBM case at the USENIX Annual Technical Conference. Now you can listen as Chris DiBona, Don Marti, Jon "maddog" Hall, and others explain the nuances of the case. Click here for the MP3."
Should this thing get all slashdotted to hell, I've got a BitTorrent mirror of the MP3 available here.
ftp://videl.ics.hawaii.edu/temp/usenix-slashdot/us enix.mp3
Mirror of MP3 just in case of Slashdotting.
80 lines of code makes quite a case? The NDA is to see 80 lines of code.
Here is an essay from a person that signed the NDA. Here is a bit you may find interesting:
Here is what I think I can say about the code I saw. The code is fairly trivial--the kind of stuff I wrote in school. The similar portions of the code were some 80 lines or so. Looking around the Net, I found close variants of the code, with the same comments and variable names, in sources other than Linux distributions. The code is not in a central part of the Linux kernel. The code does not appear to have been contributed to Linux by SCO or Caldera. The code exists in current versions of the Linux kernel.
Doesn't sound like much of a case to me. Perhaps you mean if hundreds of thousands of lines of code, that would make it quite a case.
3) The code continues to exist, violating SCO's copyrights.
Not quite.
The alleged code continues to exist because SCO refuses to tell anyone where it is.
Do some reading about the Doctrine of Laches. Basically, since SCO refuses to tell anyone where the alleged code is, then the alleged code is worthless to them. Since the code is worthless, SCO can't claim injury.
That's why the first order of business in a copyright enforcement process is to tell the infringing party what it is they're doing wrong.
By refusing to tell anyone where the alleged code is, so that it can be removed, they are essentially giving up any copyright claims they might have had.