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.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide