SCO's Evidence: This Smoking Gun Fizzles Out
Posted Aug 22, 2003 0:11 UTC (Fri) by
dwalters (guest, #4207)
In reply to:
SCO's Evidence: This Smoking Gun Fizzles Out by rfunk
Parent article:
SCO's Evidence: This Smoking Gun Fizzles Out
OK, so any Linux code that was copied from 32V appears to be in the clear, even without attribution, because 32V is indeed the public domain (because of the pre-1996 copyright laws, which AT&T carelessly didn't pay enough attention to).
Based on Eric's very thorough analysis, it's almost certaily true that the "slides 10-14" code in question was copied from 32V (and not System V, or BSD) into Linux 2.4.19.
So it's quite possible that the person or company that decided to copy the malloc code from 32V to 2.4.19, did so because they believed the code was in the public domain. However, they had no business slapping an SGI copyright and a GPL notice on it (but that fact does mean that they misappropriated anyone's legitimate copyright).
As an aside, this also means that Caldera really had no business releasing 32V along with all the other historical versions of Unix in 2002, because, according to the AT&T-vs.BSD ruling, it no longer belonged to them anyway ("Plaintiff has failed to demonstrate a likelihood that it can successfully defend its copyright in 32V").
I think this clears up any doubts that the "slide 10-14" claims are bogus, and the "slide 15" BPF code is a no-brainer, so that only leaves the "all your derivative works are belong to us" issue, as far as the PowerPoint presentation is concerned, and that seems to rest on some very shaky legal ground, as well as apparently incorrect claims about the development path of some of IBM's enterprise code (like JFS).
(
Log in to post comments)