Language Selection

English French German Italian Portuguese Spanish

Alan Cox and the End of an Era

Filed under
Linux

In the beginning, free software was an activity conducted on the margins - using spare time on a university's computers, or the result of lonely bedroom hacking. One of the key moments in the evolution of free software was when hackers began to get jobs - often quite remunerative jobs - with one of the new open source companies that sprang up in the late 1990s. For more or less the first time, coders could make a good salary doing what they loved, and businesses could be successful paying them to write code that would be given away.

The other company that made a conscious effort to sweep up relevant hacker talent is happily not only still with us, but thriving. Red Hat has recently posted excellent financial results, and remains arguably the leading open source company. Given its focus on GNU/Linux, it naturally tended to recruit the top people there - people like David Miller, Stephen Tweedie and Alan Cox.

Cox was born in Solihull, and studied at universities in Wales. He was a keen Amiga hacker, and contemplated writing an entirely new operating system for that machine, but decided that "writing file system stuff was too hard for one person to do." So he was naturally impressed to discover that a crazy Finn had done precisely that.

Rest Here




Alan Cox leaves Red Hat, suggesting company's future direction

Matt Asay: After 10 years with Red Hat as one of its highest-profile developers, Alan Cox is moving on to Intel.

I suspect the impetus for the change has much to do with Cox's interest in the "low-level stuff" that Intel needs, and Red Hat much less so. Implicit in Cox's note is an indication of where Red Hat is going: up the stack.

This shift will not happen overnight, but it very clearly has been happening.

Rest Here

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Phoronix on Graphics

Leftovers: OSS

Security Leftovers

  • Security updates for Thursday
  • OpenSSL patches two high-severity flaws
    OpenSSL has released versions 1.0.2h and 1.0.1t of its open source cryptographic library, fixing multiple security vulnerabilities that can lead to traffic being decrypted, denial-of-service attacks, and arbitrary code execution. One of the high-severity vulnerabilities is actually a hybrid of two low-risk bugs and can cause OpenSSL to crash.
  • Linux Foundation Advances Security Efforts via Badging Program
    The Linux Foundation Core Infrastructure Initiative's badging program matures, as the first projects to achieve security badges are announced.
  • Linux Foundation tackles open source security with new badge program
  • WordPress Plugin ‘Ninja Forms’ Security Vulnerability
    FOSS Force has just learned from Wordfence, a security company that focuses on the open source WordPress content management platform, that a popular plugin used by over 500,000 sites, Ninja Forms, contains serious security vulnerabilities.
  • Preparing Your Network for the IoT Revolution
    While there is no denying that IP-based connectivity continues to become more and more pervasive, this is not a fundamentally new thing. What is new is the target audience is changing and connectivity is becoming much more personal. It’s no longer limited to high end technology consumers (watches and drones) but rather, it is showing up in nearly everything from children’s toys to kitchen appliances (yes again) and media devices. The purchasers of these new technology-enabled products are far from security experts, or even security aware. Their primary purchasing requirements are ease of use.
  • regarding embargoes
    Yesterday I jumped the gun committing some patches to LibreSSL. We receive advance copies of the advisory and patches so that when the new OpenSSL ships, we’re ready to ship as well. Between the time we receive advance notice and the public release, we’re supposed to keep this information confidential. This is the embargo. During the embargo time we get patches lined up and a source tree for each cvs branch in a precommit state. Then we wait with our fingers on the trigger. What happened yesterday was I woke up to a couple OpenBSD developers talking about the EBCDIC CVE. Oh, it’s public already? Check the OpenSSL git repo and sure enough, there are a bunch of commits for embargoed issues. Pull the trigger! Pull the trigger! Launch the missiles! Alas, we didn’t look closely enough at the exact issues fixed and had missed the fact that only low severity issues had been made public. The high severity issues were still secret. We were too hasty.
  • Medical Equipment Crashes During Heart Procedure Because of Antivirus Scan [Ed: Windows]
    A critical medical equipment crashed during a heart procedure due to a timely scan triggered by the antivirus software installed on the PC to which the said device was sending data for logging and monitoring.
  • Hotel sector faces cybercrime surge as data breaches start to bite
    Since 2014, things have become a lot more serious with a cross section of mostly US hotels suffering major breaches during Point-of-Sale (POS) terminals. Panda Security lists a string of attacks on big brands including on Trump Hotels, Hilton Worldwide, Hyatt, Starwood, Rosen Hotels & Resorts as well two separate attacks on hotel management outfit White Lodging and another on non-US hotel Mandarin Oriental.

Android Leftovers