“I believe the 2.6 kernel is slowly getting buggier said the rather respectable looking man with short hair, spectacles and absolutely no beard whatsoever. What on earth could Andrew Morton know about Linux then? Quite a lot as it happens. Morton is the ‘lead maintainer’ of the Linux production kernel, and when he gets worried, we should all get worried. But who said anything about being worried? Oh, yes, I forgot to finish that quote “It seems we’re adding bugs at a higher rate than we’re fixing them.

Speaking at the LinuxTag Conference in Wiesbaden, Germany last Friday, Morton’s words sent a shockwave around the Linux developer community. Not necessarily because they disagree, but rather more because he said it at all. Perhaps the fact that he went on to say that if the statistically evidence proves his suspicions, then he will consider halting kernel development, at least on a temporary basis until enough issues have been resolved to play catch up. This would almost certainly involve a bug fix only kernel cycle, requiring developers to reallocate their time so that more is spent bug squishing. But with an increasing number of these developers being employed by IT companies with little financial interest in the legacy hardware that tends to cause most of the problems, how do you motivate them to participate happily, if at all?

What must rattle the cages of Linux developers everywhere is the timing of such a statement. Just as it is starting to gather some real momentum beyond the hobby user camp, finding a footing in the lucrative world of the business enterprise. All that the Linux evangelist needs is a spanner the size of this one to be thrown into their works. Of course, the open source diehards will argue that it’s just proof that the process works, it is being open. The same problems effect any long standing development lifecycle, but in the secretive world of proprietary development such things are kept locked down and woe betide anyone who is found responsible for leaking such commercially damaging information to the wider world. But those diehards are wrong, very wrong indeed. If anything it is proof that the oft vaunted claim that open source development responds more quickly to bug fixing is fatally flawed, particularly at the top end of the product food chain.

While Linux developers retain the tunnel vision that leads them to focus on new features at the expense of fixing old ones, the problem isn’t going to go away any time soon. I don’t for a moment predict the death of the Linux movement, but I do hope that Morton wields a big stick and hits the development process hard, and fast.

11 Years
Discussion Span
Last Post by pty

:eek: Eeek. Does anyone know if the flaws in the linux kernel are being mirrored by other *nix kernels, such as the one that powers Mac OS X, for instance? Mixing open source and proprietary systems is always a dangerous combination.


Precisely what I've been saying about open source in general for years.
There is no quality control worth speaking of, hardly any bugfixing.
When you rely solely on people doing it for the kick, you're going to accumulate a group of people who are uninterested in maintaining existing code, especially if it's code they didn't write themselves.

And when someone reports a bug he's shouted down with statements like "it's free, you get what you pay for", "just fix it and submit a patch" (never mind those get ignored if not from the core clique), "if you donate to our team you may get some time".
If there's any response at all that is, and not total silence from the developers who are basking in the light of their own glory.


Indeed, that is why vista has been in development for almost 6 years now, and still isn't released. :cheesy:


I'll go out on a limb and say that many of the bugs and problems to do with Linux legacy hardware compatibility stem from kernel development. The driver and module architecture of Linux changes from time to time IIRC.

Somewhat disturbing, but I'm sure it'll turn out okay.


2.6 brought a LOT to the table and development has been going at a fast rate.

I think if the core development team felt that there were too many bugs, and the rate of new critical bugs was higher than the critical bug-fix rate, they would freeze new features and concentrate on ironing out the problems. Linus hinted that this might happen after 2.6.16.

To be honest I think the original article was slightly sensationalist.

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.