On 30 Jun, 23:29, Andrew Halliwell <spi...@ponder.sky.com> wrote:
> strnbrg <strnbr...@gmail.com> wrote:
> > If I want to compile (and then boot into) a new kernel, is it
> > necessary that I make a new initrd too? *Or can I stick with the
> > (working) initrd that came with my Linux distribution (SuSE 10.3),
> > which has been working just fine? *(SuSE 10.3 installed a 2.6.22.5
> > kernel, and I want to compile a 2.6.25.6.
>
> Kernel modules stored in initrd are specificly for the kernel the initrd was
> made with, so yep, you'll need to mkinitrd...
>
> UNLESS... you compile your kernel with the things required for booting
> compiled INTO the kernel, rather than as modules.

Doing this for SuSE is awkward: the 'YaST' GUI is absolutely awful
about dealing with multiple kernels, especially home-grown kernels,
and tends to flush your old kernel when doing RPM kernel updates. I
ran into this a lote with SuSE 9.x.