Linked by Eugenia Loli on Mon 22nd Dec 2003 06:43 UTC
SCO, Caldera, Unixware The SCO Group plans to announce Monday that it is escalating its campaign to collect license fees from corporations using the Linux OS, with warning letters to the companies. Supporters of Linux, including IBM and other companies, say that SCO's interpretation of its claim over Linux is exaggerated.
Permalink for comment
To read all comments associated with this story, please click here.
Details
by Jud on Mon 22nd Dec 2003 16:51 UTC

SCO hasn't provided the files yet. Yes, when they do it will be under a protective order because there simply wasn't any point in IBM objecting to that (as long as IBM gets to see the files there's no reason to object that anyone else won't see them), in spite of the fact that it is ludicrous for SCO to claim files are confidential after SCO itself agrees they have already been disclosed on a worldwide basis in the Linux kernel.

SCO has said it is refusing to disclose the files publicly because then they could be changed in Linux to "cover the tracks" of the violations. This of course is another absurdity, since code submissions to the Linux kernel are public. It's not as if IBM, Linus, or anyone else can suddenly fake years' worth of kernel mailing list archives (and even if they were to try, all SCO has to do is make its own local copy, thus preserving all records of any alleged violations).

No one responding to this item has mentioned in any detail what SCO's latest notice is saying. According to SCO, it has notified recipients of the notice of 65 "application binary interface" files (that's right, *not* API) in Linux that infringe SCO's intellectual property rights. These files are apparently identified in an attachment to the notice. SCO additionally mentions that the 65 files were involved in the AT&T vs. BSD litigation that was settled years ago. So if anyone can get hold of a copy of a notice, we'll all know at least 65 files that SCO claims infringe on its rights, and we can all look at the publicly available sources to see when and from where they got into the Linux kernel. Ask your friends if they've received a notice! ;)