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

Security Leftovers

  • Someone is putting lots of work into hacking Github developers [Ed: Dan Goodin doesn't know that everything is under attack and cracking attempts just about all the time?]
    Open-source developers who use Github are in the cross-hairs of advanced malware that has steal passwords, download sensitive files, take screenshots, and self-destruct when necessary.
  • Security Orchestration and Incident Response
    Technology continues to advance, and this is all a changing target. Eventually, computers will become intelligent enough to replace people at real-time incident response. My guess, though, is that computers are not going to get there by collecting enough data to be certain. More likely, they'll develop the ability to exhibit understanding and operate in a world of uncertainty. That's a much harder goal. Yes, today, this is all science fiction. But it's not stupid science fiction, and it might become reality during the lifetimes of our children. Until then, we need people in the loop. Orchestration is a way to achieve that.

Leftover: Development (Linux)

  • Swan: Better Linux on Windows
    If you are a Linux user that has to use Windows — or even a Windows user that needs some Linux support — Cygwin has long been a great tool for getting things done. It provides a nearly complete Linux toolset. It also provides almost the entire Linux API, so that anything it doesn’t supply can probably be built from source. You can even write code on Windows, compile and test it and (usually) port it over to Linux painlessly.
  • Lint for Shell Scripters
    It used to be one of the joys of writing embedded software was never having to deploy shell scripts. But now with platforms like the Raspberry Pi becoming very common, Linux shell scripts can be a big part of a system–even the whole system, in some cases. How do you know your shell script is error-free before you deploy it? Of course, nothing can catch all errors, but you might try ShellCheck.
  • Android: Enabling mainline graphics
    Android uses the HWC API to communicate with graphics hardware. This API is not supported on the mainline Linux graphics stack, but by using drm_hwcomposer as a shim it now is. The HWC (Hardware Composer) API is used by SurfaceFlinger for compositing layers to the screen. The HWC abstracts objects such as overlays and 2D blitters and helps offload some work that would normally be done with OpenGL. SurfaceFlinger on the other hand accepts buffers from multiple sources, composites them, and sends them to the display.
  • Collabora's Devs Make Android's HWC API Work in Mainline Linux Graphics Stack
    Collabora's Mark Filion informs Softpedia today about the latest work done by various Collabora developers in collaboration with Google's ChromeOS team to enable mainline graphics on Android. The latest blog post published by Collabora's Robert Foss reveals the fact that both team managed to develop a shim called drm_hwcomposer, which should enable Android's HWC (Hardware Composer) API to communicate with the graphics hardware, including Android 7.0's version 2 HWC API.

today's howtos

Reports From and About Cloud Native Computing Foundation (CNCF)