[Bug 636904] [NEW] /lib/modules directories left behind after purging kernels

[Matt Zimmerman]

Public bug reported:

I purged a bunch of old kernels yesterday, and noticed (via the warnings
from dpkg) that their /lib/modules directories remained on the system:


perseus:[~] ls /lib/modules                 
2.6.28-10-generic  2.6.30-9-generic  2.6.31-7-generic   2.6.35-20-generic
2.6.28-8-generic   2.6.31-1-generic  2.6.32-23-generic  2.6.35-6-generic
2.6.28-9-generic   2.6.31-2-generic  2.6.32-9-generic   2.6.35-7-generic
2.6.30-10-generic  2.6.31-3-generic  2.6.35-10-generic  2.6.35-8-generic
2.6.30-6-generic   2.6.31-4-generic  2.6.35-11-generic
2.6.30-7-generic   2.6.31-5-generic  2.6.35-15-generic
2.6.30-8-generic   2.6.31-6-generic  2.6.35-19-generic

A purge operation should remove these traces.

The older (2.6.28) directories contain:
modules.alias.bin  modules.dep.bin  modules.symbols.bin

The newer (2.6.32 and .35) contain:
modules.devname  modules.softdep

I also came across one which has:
/lib/modules/2.6.32-9-generic:
modules.builtin.bin

The presence of these files will prevent dpkg from cleaning up the
otherwise-empty directory created by the package.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: packaging

** Tags added: packaging

-- 
/lib/modules directories left behind after purging kernels
https://bugs.launchpad.net/bugs/636904
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.