Bug 35587 – emerging kernel modules for a new kernel deletes those modules from the old kernel

• Product: Portage Development
• Status: RESOLVED DUPLICATE

[Description Philip Hazel 2003-12-11 01:57:21 UTC]

When you build a new kernel with a new name (e.g. from a new source) and then
emerge something that installs kernel modules (e.g. alsa-driver), the emerge
process deletes the old version of the modules - which belong to your old kernel!
This is not good if you want to preserve the ability to reboot your old kernel.
There should be some way to prevent this, and preferably it should be automatic.

Reproducible: Always
Steps to Reproduce:
1. Build a new kernel with a new name (so it uses a different /lib/modules dir)
2. Emerge something that makes a kernel module (alsa-driver, e1000, etc.)
3. Watch it remove the old modules that belong to your running kernel.

Actual Results:  
You have to reemerge the modules if you want to return to your old kernel

Expected Results:  
I didn't expect it to remove stuff from the old kernel's modules directory.

[Comment 1 SpanKY 2003-12-11 08:01:58 UTC]

*** This bug has been marked as a duplicate of 1477 ***