On Thu, 3 May 2001, Paul W. Abrahams wrote:
Let's say I've decided that from now on I always want to work with a kernel I've compiled myself, and that furthermore I stick to the SuSE sources. I know how to compile a kernel and install the results (it's not that hard). But how do I ensure that the files created by the compilation (including modules) don't cause confusion within the rpm database of what's installed and what isn't?
If you compile your own kernel and install it using "make modules_install", it will overwrite the currenly installed modules from the kernel RPM (k_deflt, for example - if the kernel verisions are the same, of course). If you want to go with your self compiled kernel, you should remove k_deflt first. Don't forget to run "mk_initrd" and lilo again, after you have run "make bzlilo"! Bye, LenZ -- ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH mailto:grimmer@suse.de Schanzaeckerstr. 10 http://www.suse.de/~grimmer/ 90443 Nuernberg, Germany One who is always in a stew generally goes to pot.