Home opinion-and-analysis Open Sauce LTS kernel for embedded vendors

Author's Opinion

The views in this column are those of the author and do not necessarily reflect the views of iTWire.

Have your say and comment below.

The yearly, or thereabouts, kernel development report put out by the Linux Foundation has a couple of bits of interesting information.

One relates to the creation of a long-term support initiative to provide a stable base for embedded products.

The initiative was announced last year. Every year there will be one release of a kernel suited to embedded products; this will then be maintained for two years. It gives certainty to businesses and reduces their overall costs. It also provides a means of paying the developer who handles the maintenance.

In the Foundation's own words: "The project creates and maintains a long-term industry tree, which is expected to be stable in quality for the typical lifetime of a consumer electronics product, typically 2-3 years."

Companies like Samsung and Sony are supporters of the initiative for obvious reasons.

The report, which covers kernel releases from 2.26.32 to 3.2, has loads of other statistics that show how development progresses, its speed and how many people and companies are involved. I'll deal with these in detail separately.

An interesting statistic is that Microsoft is now among the top 20 corporate contributors to the kernel. But given the fact that it wants to play in the server and virtual spaces, Microsoft really has no option but to ensure that its products work well with Linux. The boot is now well and truly on the other foot in the server and embedded markets.

FREE WHITEPAPER - RISKS OF MOVING DATABASES TO VMWARE

VMware changed the rules about the server resources required to keep a database responding

It's now more difficult for DBAs to see interaction between the database and server resources

This whitepaper highlights the key differences between performance management between physical and virtual servers, and maps out the five most common trouble spots when moving production databases to VMware

1. Innacurate metrics
2. Dynamic resource allocation
3. No control over Host Resources
4. Limited DBA visibility
5. Mutual ignorance

Don't move your database to VMware before learning about these potential risks, download this FREE Whitepaper now!

DOWNLOAD!

Sam Varghese

website statistics

A professional journalist with decades of experience, Sam for nine years used DOS and then Windows, which led him to start experimenting with GNU/Linux in 1998. Since then he has written widely about the use of both free and open source software, and the people behind the code. His personal blog is titled Irregular Expression.

Connect