Language Selection

English French German Italian Portuguese Spanish

Red Hat's Jim Whitehurst: "I Want to Meet Linus"

Filed under
Linux
Interviews

Red Hat CEO Jim Whitehurst is speaking this year at LinuxCon on opening day about the challenges that still lie ahead as we embark on another 20 years of Linux. We wanted to know more about Whitehurst's perspective as we prepare for the big event and the formal celebration of the 20th anniversary of Linux. Here's what he told us.

The Linux operating systems turns 20 years-old this year, and Red Hat is a huge part of its story. How do you view Linux and its future as we begin to celebrate this important milestone?

Whitehurst: Linux is clearly the operating system driving web 2.0 and cloud computing. Virtually any new application and/or any new web start-up is building a Linux-based stack. That's huge: Linux has gone from being a "viable alternative" to traditional operating systems to being the "default choice." We should all be very proud of that.

rest here

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.