Slashdot Mirror
2.6 Linux Kernel in Need of an Overhaul?
toadlife writes "ZDNet UK reports that Andrew Morton, the head maintainer of the Linux production kernel, is concerned about the amount of bugs in the 2.6 kernel. He is considering the possibility of dedicating an entire release cycle to fixing long standing bugs." From the article: "One problem is that few developers are motivated to work on bugs, according to Morton. This is particularly a problem for bugs that affect old computers or peripherals, as kernel developers working for corporations don't tend to care about out-of-date hardware, he said. Nowadays, many kernel developers are employed by IT companies, such as hardware manufacturers, which can cause problems as they can mainly be motivated by self-interest."
"This is particularly a problem for bugs that affect old computers or peripherals, as kernel developers working for corporations don't tend to care about out-of-date hardware, he said. Nowadays, many kernel developers are employed by IT companies, such as hardware manufacturers, which can cause problems as they can mainly be motivated by self-interest.""
I suggest we have some more unemployed kernel developers to correct this problem.
Hurd is currently due for release shortly after Duke Nukem Forever.
Day 1 - Andrew's kernel is "stolen" under strange circumstances.
Day 2 - Chip Foose draws up a design for the kernel, the coding commences.
Day 3 - Andrew receives a call from a "kernel repo man". Apparently his kernel was taken by mistake.
Day 4 - Coding like mad. Fake repo man stalls Andrew. The crew is running out of Doritos.
Day 5 - The pressure mounts. Token pretty face "helps out" by typing "make" in a staged moment of tension.
Day 6 - We're never gonna get the kernel done in time!!!! Oops and panic. Fake repo man stalls again.
Day 7 - The reveal. A shiny new kernel is handed back to Andrew. You've been OVERHAULED!
Anybody want a peanut?
So, there are lots of bugs in Linux! Good thing I'm using Windows.
w00t
Promise me you'll never EVER say that out loud. Please.
Yes, yes, "borgheron", we all know its you Mr Tanenbaum, you don't need to hide behind a silly moniker. You're not *still* pissed at Torvalds after all these years are you? :-)
Bluescreen? Sometime last year, don't recall why.
Spontaneous reboot? A couple of weeks ago.
Inexplicably corrupt registry after running Windows Update? Last week.
Throttling the CPU down to 600MHz and then reporting that as the maximum speed? A couple of days ago.
Obviously, to have the very best bugs.