Language Selection

English French German Italian Portuguese Spanish

Linux for desktop should 'catch fire' by 2008

Filed under
SUSE

Novell has launched the next version of its desktop Linux OS, a release the company hopes will begin a "viral" migration from Windows in the next several years, said Jeff Jaffe, chief technology officer for Novell.

Novell SuSE Linux Enterprise Desktop 10 (SLED 10) is the first version of Novell's desktop Linux that is "good enough" for enterprises to replace Windows in more than just limited deployments, Jaffe said.

"Our new SuSE Linux Enterprise Desktop now meets the needs of the basic office worker," he said.

Full Story.


Novell announced on March 9 that it has hired a new executive to run its Linux and open source business unit.

Roger Levy, formerly with Lucent Technologies, has been named general manager of the Open Platform Solutions business unit. He will report to Jeff Jaffe, executive vice president and CTO. At Lucent, Levy had held several executive development and business positions.

Levy will be replacing David Patrick, who will be pursuing interests outside of Novell.

That Story.

More in Tux Machines

Red Hat News

Development News: LLVM, New Releases, and GCC

PulseAudio 10 and Virtual GPU in Linux

  • PulseAudio 10 Coming Soon, Using Memfd Shared Memory By Default
    It's been a half year since the debut of PulseAudio 9.0 while the release of PulseAudio 10 is coming soon. PulseAudio 9.99.1 development release was tagged earlier this month, then usually after x.99.2 marks the official release, so it won't be much longer now before seeing PulseAudio 10.0 begin to appear in Linux distributions.
  • Experimenting With Virtual GPU Support On Linux 4.10 + Libvirt
    With the Linux 4.10 kernel having initial but limited Intel Graphics Virtualization Tech support, you can begin playing with the experimental virtual GPU support using the upstream kernel and libvirt.

Licensing FUD and Licensing Advice

  • On the Law and Your Open Source License [Ed: Black Duck is just a parasite selling proprietary software by bashing FOSS]
    "Looking back five or ten years, companies managing open source risk were squarely focused on license risk associated with complying with open source licenses," notes a report from Black Duck Software. Fast-forward to today, and the rules and processes surrounding open source licensing are more complex than ever.
  • Explaining the source code requirement in AGPLv3
    This condition was intended to apply mainly to what would now be considered SaaS deployments, although the reach of "interacting remotely through a computer network" should perhaps be read to cover situations going beyond conventional SaaS. The objective was to close a perceived loophole in the ordinary GPL in environments where users make use of functionality provided as a web service, but no distribution of the code providing the functionality occurs. Hence, Section 13 provides an additional source code disclosure requirement beyond the object code distribution triggered requirement contained in GPLv2 Section 3 and GPLv3 and AGPLv3 Section 6.