The Kernel Is All Paid Up
One of the great things about Linux and Open Source in general is that, despite perceptions to the contrary, we aren't going it alone. A number of corporate and institutional sponsors — Red Hat, Google, the Linux Foundation, to name a just a few of the many — back the continued development of Open Source software, contributing not just funds, but employee time to the cause.
The annual linux.conf.au has its share of time-honored features: Open Day, the Penguin Dinner, and of course, Jonathan Corbet's The Kernel Report. The annual talk — established enough to be described as "the usual talk that we know and love" — runs down the latest developments in kernel development and presents a general "state of the kernel" address that hits the high points of where the community is and where it's going.
This year's report, presented last Wednesday in Wellington, New Zealand, offered an interesting look not only at where the kernel is, but who was behind it — and who footed the bill. The great revelation, at least as some third-party accounts would have it, is that three-quarters of the code contributed to the Linux kernel comes from developers paid to write it. Corbet reported that just 18% of the work being done came from those without corporate backing, with a mysterious 7% coming from the unknown.
As one might expect, the top corporate contributors were those with heavy investments in Open Source — six percent each from Novell and IBM, eight percent from Intel, and a full twelve percent from Red Hat. The number five position went to a company headlining Open Source news at the moment: Oracle, the great horned beast waiting to devour MySQL, contributed three percent of the kernel's code, far more than Linus himself. (Linus' contribution is, of course, measured by far more than just lines of code.)
None of this will come as a surprise to Linux Journal readers — and we suspect, did not to linux.conf.au attendees or Corbet himself — who will recall all of the above from the second edition of Linux Kernel Development: How Fast it is Going, Who is Doing It, What They are Doing, and Who is Sponsoring It?, published in August by the Linux Foundation.
Justin Ryan is a Contributing Editor for Linux Journal.
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- Dynamic DNS—an Object Lesson in Problem Solving
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Tech Tip: Really Simple HTTP Server with Python
- Roll your own dynamic dns
3 hours 54 min ago
- Please correct the URL for Salt Stack's web site
7 hours 5 min ago
- Android is Linux -- why no better inter-operation
9 hours 20 min ago
- Connecting Android device to desktop Linux via USB
9 hours 49 min ago
- Find new cell phone and tablet pc
10 hours 47 min ago
12 hours 16 min ago
- Automatically updating Guest Additions
13 hours 24 min ago
- I like your topic on android
14 hours 11 min ago
- This is the easiest tutorial
20 hours 47 min ago
- Ahh, the Koolaid.
1 day 2 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?