Check out the refute:refutation

The obfuscated sample, which contains networking software, could have been legitimately copied in the Linux source code, because it has been released under a BSD license, Perens said.

But the code was created from scratch and not copied from any version of Unix, according to the Linux developer who contributed it.

Jay Schulist, a senior software engineer with Pleasanton, California's Bivio Networks says he wrote the 500 lines of code in 1997 as part of a volunteer project for the Stevens Point Area Catholic Schools in Wisconsin. "I used it for helping a local school district in my home town to connect their old Apple Macintosh machines to the Internet," he said.

Schulist wrote the code, based on the publicly available specifications created by Lawrence Berkeley Labs, he said. He has never seen the AT&T source code, he added.

The Linux hacker expressed surprised that his contribution would be singled out by SCO. "I have no idea why they would even chose my code," he said. "If they had done any research at all, they would have realized that there was no other way to implement the actual filtering engine."

Update Warning: photo at this url is not for the sqeamish. View at your own disgression. lawyer-of-the-year

In reply to Re: OT: SCO vs Linux - first publicly released evidence by zentara
in thread OT: SCO vs Linux - first publicly released evidence by Aristotle

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.