depclean would like to clean old (but used) kernel

Dominique_71 · Posted: Fri Apr 25, 2008 7:19 pm Post subject:

I love gentoo too. And I know that the gentoo programmers are doing a really great job. And I am very grateful for this. The problem is not here.

The files in /boot and /lib/modules are not managed by portage. I would really like to have a portage setting that would let me choose if I want that portage manage or not the old kernel sources. In other words, why is it necessary to use another syntax as the usual "emerge <package>" with the kernel related packages in order to not get system breakage?

Another correct way for me would be if portage would check if the kernel is present in /boot and/or /lib/modules and remove the sources only if the kernel is not installed.

This should also be extended to external kernel modules like the alsa driver or the nvidia driver. Why, with the default syntax, is portage removing the old versions when the related kernels are still installed? It is pure non sens !
_________________
"Confirm You are a robot." - the singularity

benny1967 · Apprentice Joined: 25 Apr 2004 Posts: 224

I found this thread today because I noticed a strange behavior when I tried to emerge sys-apps/v86d-0.1.3-r1

The (shortened) error is:

Dominique_71 · Posted: Tue May 27, 2008 6:33 pm Post subject:

For now, I can keep old kernel sources by adding them into /var/lib/portage/world. I don't like this, but it work.

But what about external kernel modules like the nvidia driver. Each time I or portage want to emerge the nvidia driver, portage want to remove the old version, and that even when it is the same version, but compiled for another kernel.

Is it some way to keep the version of the nvidia (or alsa or whatever external one) driver compiled for another kernel?
_________________
"Confirm You are a robot." - the singularity