Linked by Thom Holwerda on Sat 6th May 2006 17:26 UTC, submitted by JMcCarthy
Linux Andrew Morton, the lead maintainer of the Linux production kernel, is worried that an increasing number of defects are appearing in the 2.6 kernel and is considering drastic action to resolve it. "I believe the 2.6 kernel is slowly getting buggier. It seems we're adding bugs at a higher rate than we're fixing them," Morton said, in a talk at the LinuxTag conference in Wiesbaden, Germany, on Friday.
Thread beginning with comment 122177
To read all comments associated with this story, please click here.
RE[4]: Million times
by kaiwai on Mon 8th May 2006 05:40 UTC
Member since:

Are you sure about this? How many times have you changed your kernel configuration and found that most of your applications are broken?

Why can't I run a kernel moduled, compiled with GCC 3.4 on a kernel compiled with GCC 3.0?

All sane "API specifications" include calling conventions. That's why your applications don't break when you modify the kernel, and that's why all compilers can support the stable API.

And if you read Linus's statement on that, it would be alot clearer for you - but hey, ignore them if you wish, you've done already.

There's only 2 "valid" problems with creating a stable API for device drivers. The first problem is the GPL/open source mentality, where it's not "fashionable" to allow other peoples work to be closed source. The second problem is backwards compatibility, which can be solved in a number of ways.

I don't see it as an 'opensource' or 'GPL mentality', because there are already GPL software out there, quite happy to provide backwards compatibility, even for the so-called 'evil proprietary software vendors'.

The last way would be to ditch the buggy "mega-beast" and switch to a micro-kernel (there was an article about this)... :-)

How the hell does that fix the problem? you'll still require a stable API, and assuming that the microkernel is developed by linux god himself, you're going to be saddled with the same crap.

There was a solution provided by Calderae, the UDK - no one caught onto it; had that been adopted, and made the driver API standard for Linux, we wouldn't be having these parlour games today - life would have moved on, and we would be moaning about important things.

Reply Score: 2