On Monday 10 Dec 2001 10:16 pm, Anders Johansson wrote:
On Monday 10 December 2001 23.10, Tim Harrell wrote:
The issue is that when I do a modules_install, won't those modules still be lying around in /lib/modules?
The flag EXTRAVERSION in the top level Makefile was set to -4GB in suses compilation. In my makefile it's clean, but you can set it to, say, -tim. That way, the modules will land in /lib/modules/2.4.x-tim, and they won't collide with the original modules. That way you can also keep the old kernel + modules, so you have a known working kernel to fall back on, in case the compile is a failure.
regards Anders
Thanks Anders, that's exactly what I was looking for.
I knew all about keeping the old kernel accessible in lilo to fall back on
but I was wondering how one could possibly unpick it if the modules had been
seriously screwed up.
The makefile I have has -4GB as HIGHMEMVERSION in the building of the kernel
release string so I'd get something like
2.4.7-tim-4GB
Regards,
--
Tim Harrell