Language Selection

English French German Italian Portuguese Spanish

SCO bites back on Linux memo claims

Filed under
Linux

The 2002 e-mail, published by Internet law site Groklaw as part of its ongoing coverage of SCO's copyright infringement claims against Linux vendor IBM and user Autozone, was sent to a senior vice president at the company by an in-house engineer and later forwarded on to chief executive Darl McBride.

"At the end, we had found absolutely nothing ie (sic) no evidence of any copyright infringement whatsoever," engineer Michael Davidson wrote of his and an external consultants' attempts to find copyrighted Unix code in Linux.

However, SCO said in a statement this afternoon, "it would simply be inaccurate - and misleading -- to use Mr Davidson's e-mail to suggest that SCO's internal investigation revealed no problems."

SCO e-mailed the media a memo sent in 1999 from that external consultant, Robert Swartz, to SCO's Steve Sabbath, who was at the time the company's general counsel. The memo details Swartz's initial findings which -- according to the vendor -- demonstrate there is cause for concern as to whether portions of protected Unix code were copied into Linux.

"This memo shows that Mr. Davidson's e-mail is referring to an investigation limited to literal copying, which is not the standard for copyright violations, and which can be avoided by deliberate obfuscation, as the memo itself points out," the company continued. SCO also pointed out its legal wrangling with IBM dealt with more recent versions of the Linux code than were mentioned in the memo.

"Even more importantly, this memo shows that there are problems with Linux. It also notes that additional investigation is required to locate all of the problems, which SCO has been continuing in discovery in the IBM and Autozone cases," said SCO.

SCO sued IBM in 2003 for more than US$1 billion, alleging that IBM had misappropriated Unix technology to which SCO claimed intellectual property rights.

Source.

More in Tux Machines

Why the Open Source Stars Must Align

Open source projects like OpenStack, Docker, OPNFV and OpenDaylight are more supported and better funded than ever before. They mark a broader trend of large, active and well-resourced open source projects that are among the leaders in Big Data, cloud computing, operating systems and development practices. Open source has come a long way in 30 years – and its success marks a new era for the overall OSS community. But success does not come without potential pitfalls. One of the greatest obstacles to project success isn’t the proprietary competition – it’s the lack of communication between large open source projects like OpenStack and Docker. Read more

Myth Busting the Open-Source Cloud Part 1

On the contrary, open-source cloud computing products are designed from the outset with security in mind. For example, there are features such as identity management to monitor who has access to content, and data encryption to safeguard information while it’s at rest or in transit. Furthermore, open-source cloud software is peer-reviewed by community participants, leading to continuous improvements in the quality of security features and mechanisms. This community also monitors and rapidly discloses vulnerabilities and issues, and provides security updates to address them. Read more

What does an adult look like in an open source community?

You're no longer "just an adult." You're now trusted and looked to for opinions on how the community should grow. You're a community elder. You embody the history. You keep the history. You work together with other adults and elders to guide and make the community stronger. And to a certain extent, the community once again looks after you, just as it did in the first phase. Read more