I've been running custom kernels on debian systems for about 7 years without running into any problems
it depends on how you define 'the standard linux way'
are you using make install to install the kernel? (works if you are installing it on the kernel you build it on)
are you using the make system to create a .deb/.rpm file (I don't remember the make command for this, is it make kpkg?)
if you are doing neither, then you have the same problem that you can have an any distro, the modules directory is per kernel version, and if you don't compile all the modules you need you may end up using modules that were compiled from a prior version.
I avoid these problems by not using modules for my production servers. This lets me just worry about installing the kernel file itself on the systems.
Posted Jul 28, 2010 2:37 UTC (Wed) by deater (subscriber, #11746)
[Link]
I guess we all have different definitions of "real world". Unfortunately in my world, I don't have root access on most machines I use day to day, and I also don't control what kernel gets booted on them. The world of being a plain user is very different from that of a kernel dev.
Sure, but what this has to do with anything?
Posted Jul 28, 2010 6:39 UTC (Wed) by khim (subscriber, #9252)
[Link]
If you can't replace kernel then that's your problem: escalate to someone who can replace kernel. If noone can replace kernel then kernel developers have nothing to do with it - it's your own mess and you must to something with it.
Try to ask motor mechanic to fix you car without opening the hood sometime and hear what he thinks about this idea.