Noriaki's picture

LTSI Kernel Maintainer Greg Kroah-Hartman has released the latest version of LTSI Kernel (3.0.79-LTSI and 3.4.46-LTSI) on May 21.

 

The followings are the changes that have been merged for each release.

 

3.0.79-LTSI:

libbyclark's picture

LinkSmart’s audience and link management platform for publishers was built with big data at its core. So when management decided to migrate the cloud-based application to their own hardware, there was no question it would be completely powered by Linux. 

Linux-based infrastructure allows the 3-year-old startup to cut costs, both by avoiding the licensing fees of proprietary systems and by tapping the community’s collective knowledge base instead of paying for expensive support contracts, said CTO Manny Puentes.

gregkh's picture

A few years ago, I gave a history of the 2.6.32 stable kernel, and mentioned the previous stable kernels as well. I'd like to apologize for not acknowledging the work of Adrian Bunk in maintaining the 2.6.16 stable kernel for 2 years after I gave up on it, allowing it to be used by many people for a very long time.

I've updated the previous post with this information in it at the bottom, for the archives. Again, many apologies, I never meant to ignore the work of this developer.

Corbet's picture

Linus Torvalds made a Mother's Day gift to the world in the form of the 3.10-rc1 kernel prepatch. With this release, the merge window for the 3.10 development cycle has closed, so we know which features to expect this time around.

jzemlin's picture

Today we’d like to welcome Xen as the newest Linux Foundation Collaborative Project.

The Xen Project is 10 years-old this week, and its contributors have doubled in the last few years. Xen usage continues to grow and today the project is being deployed in public IaaS environments by some of the world's largest companies. 

mricon's picture

Are you a systems administrator? Quick, which system in your infrastructure is most vulnerable to hacker attacks? No, it’s not the web server -- though it’s a good guess. No, it’s not the firewall. The answer may surprise you -- it’s your workstation.

jejb's picture

Guest post from James Bottomley, Linux Foundation Technical Advisory Board