Daniel Robbins wrote: >> Something I couldnt see from from your explanation: does it leave existing >> modules in place if you change your kernel? If it does it will be the >> answer to my prayers as I am currently building kernels ... > > The latest Portage (-r18) should leave existing modules in place.
As I discovered earlier today, the latest 2.0.49-r18 in the portage tree does not contain the fixed portage.py file to prevent existing modules from being removed. Until the fixes make it into a portage a workaround is to set the CONFIG_PROTECT variable on the command line where you run the emerge command. For example, while I was testing this I had gentoo-test-r1 as my main kernel. For the testing, I installed gentoo-sources-r9. After I changed /usr/src/linux to point to /usr/src/linux-2.4.20-gentoo-r9, I ran kernelmod-rebuild with the following command: env CONFIG_PROTECT="/lib/modules/2.4.22-gentoo-test-r1" kernelmod-rebuild --quiet -- --verbose This resulted in my third-party kernel modules being rebuilt for the gentoo-sources kernel and left the modules for the gentoo-test kernel in place. I would not recommend setting this in the make.conf file as when you reinstall one of the packages for a kernel where you have already installled the package, you typically want the old modules to be overwritten. Regards, Paul -- [EMAIL PROTECTED] mailing list
