
To view parent comment, click here.
To read all comments associated with this story, please click here.
"You cannot take an arbitrary custom kernel, chuck it into an arbitrary Linux distro and expect it to magically work. That is hardly bug."
Well, yes and no. One of the strengths of Linux is that you CAN do that. Look on any blog or anywhere on the net and that is touted as one of the biggest benefits. Comments like "If you don't like the distro's kernel, just compile your own" are very commonly made. What is not said though is that once you DO plug your custom kernel into the distro's framework, you can no longer rely on the distro's updates for any software, without suffering the same fate of the system not booting.
What is not said though is that once you DO plug your custom kernel into the distro's framework, you can no longer rely on the distro's updates for any software, without suffering the same fate of the system not booting.
Unless the distro has patched something you don't like, you should really use the distro's kernel source and config as a starting point to roll your own kernel. Far less headaches that way.
I've done this on some production servers and it works reasonably well, although recompiling after every kernel update is a PITA.
No, it's not said.
Then again, why would anybody expect somebody who was such a novice to start rolling their own kernel?
Seriously, if I roll my own (especially if I've done any amount of reading on the subject) I know that I shouldn't then do a dist-upgrade from ubuntu, allowing it to essentially overwrite what I've done.
Sorry, but if somebody is a novice they shouldn't be custom compiling kernels on a production system. If anything test it a bit first.
Member since:
2005-07-06
You cannot take an arbitrary custom kernel, chuck it into an arbitrary Linux distro and expect it to magically work. That is hardly bug.