> Anyway, thanks for the thoughts; but I do still want a working ipmi :). > No biggie to add one line and recompile the kernel, but it would be nice > to get fixed. It's still disabled by default out of the box, you have to > explicitly reconfigure your kernel to enable it.
If you want it working, you will need to get it fixed. On all machines, so that we can renable it. Or the process you just described will go terribly wrong soon. Let me explain how we work. When we disable something -- as ipmi was handled -- it means we have give up on trying to fix it. This code was locking up some machines and noone cared enough to find the problem and fix it permanently. However, if code is disabled it also means people suddenly aren't using it, being exposed to the bug, and caring about it. Obviously a majority of users don't use this code. Also that means a majority of developers aren't using it. I'd say that number is ZERO. So in more than 5 years, noone has arrived to take care for it. But someone needs to care for every piece of code in our tree. Indications are noone will take care of ipmi.c So before long, the tedu will arrive with his scythe and take the code to the other world. I predict it won't be long before the code we don't use, don't maintain, and which noone else maintains is gone. Actually, this may summon the tedu...
