Curtis Rey wrote:
<snip> I strongly suggest that this is very (repeat very) likely the case. I think that unless there's code that McBride and company claims is in the kernel and it isn't referenced in any of the changelogs or submission records then this could be a problem. But If it is shown that said violating code is referenced to one of SCO's devs or employees then the case/claims are mute and SCO is in a heap of sh**!
So should someone perhaps be documenting all the locations in the code that have references to SCO (and perhaps other keywords, like UNIX)? For x-ref purposes? And perhaps trying to determine the date the reference first shows up? I'd guess there would be a bouncing of dates between the first Linux entry and the first Unix entry, ie. cross-pollination, not uni-directional pollination. (And I'd guess that there is sufficient GPL'd code in UNIX that UNIX itself is in violation of GPL.)