You probably remember the whole thing about FatELF and my assertion that FatELF does nothing to solve what the users supporting it want to see solved: multiple architecture support by vendors. I’d like to explain somewhat further what the problem is in my opinion.

Even though the idea of formal alignment between the freezes of Debian and Ubuntu didn't hold, there has been some good practical collaboration between the maintainers of key subsystems. There are real benefits to this, because maintainers have a much more fruitful basis for sharing patches when they are looking at the same underlying version.

Recently Greg Kroah Hartman showed some very interesting Linux kernel development stats. I decided to do some too and the result are 5 cool things you probably didn’t know about the kernel code

Linux's first-ever official "embedded maintainers" have invited device developers to get involved in the kernel development process.

The Linux kernel is surrounded by hundreds of interested parties. How is it that none of them gains a commanding influence over the kernel's development priorities?HP, IBM, Oracle. Google, eBay and Intel each has a primary stake in Linux and employs kernel developers. Does this mean money talks when it comes to Linux? If not, why not?

Rusty Russell posted on LKML some patches to add documentation for his actual kernel work known as lguest. In one of his patches Rusty wrote:”Indeed, no code changes, and I feel strongly that it should go into 2.6.23 because it’s fun. And (as often complained) there’s not enough poetry in the kernel.”

wine patches the black hole of code? Patches rarely receive feedback - positive or negative - on the wine-patches list. Patches that are rejected aren't labelled as such, or publicly given a reason for why they were. Hundreds of patches don't get in, that just need a tweak or two, that would REALLY improve the wine experience.

David Airlie has just called upon Linus Torvalds to pull in the latest DRM patches for inclusion into the Linux 2.6.33 kernel. The Direct Rendering Manager improvements in this next kernel release will be particularly interesting.

After the release of Linux 2.6.27, kernel developers are currently busily integrating patches for the next kernel version into the main development branch of Linux. This usually involves discarding some old code and adding new code though on balance, there are usually more new lines than old ones, making the kernel grow continually.