Main development phase of Linux kernel 2.6.36 completed
Summary
With Linux 2.6.36-rc1, the merge window, in which most new features enter the main branch, ended in August 2010. Among other things, the AppArmor security framework was accepted after years of attempts, as were fanotify for virus scanners and a driver for Intel’s Intelligent Power Sharing. As with 2.6.35, Torvalds wanted to accept strictly only bug fixes in the following stabilisation phase.
Ideas
- AppArmor had been in use at openSUSE and Ubuntu for some time before it came into the kernel.
- fanotify gives virus scanners access to file events on opening.
- Strict handling of late patches is meant to avoid new bugs.
Insights
- A fixed development rhythm makes kernel releases predictable.
- Distributions often carry features as patches for years before they become mainline.
Facts
- The stabilisation phase typically lasted nine to twelve weeks.
- Rudimentary KMS support for Nvidia’s Fermi chips was also added.
References
Critique
- The list of many new features leaves open which of them are of practical relevance to server operators.
Recommendations
- Use mandatory access control such as AppArmor or SELinux for exposed services.
- Follow merge windows to recognise early which features your distribution will soon receive.
Links to the original source and the Web Archive open in a new tab.