Boyd Stephen Smith Jr. wrote:
On Wednesday 02 June 2010 10:47:26 H.S. wrote:On 02/06/10 11:19 AM, Tom Furie wrote:On Wed, Jun 02, 2010 at 11:10:09AM -0400, H.S. wrote:H.S. wrote:Now, after doing this, I still have this kernel in /boot: $> ls -1 /boot/*trunk* /boot/config-2.6.32-trunk-686 /boot/initrd.img-2.6.32-trunk-686 /boot/initrd.img-2.6.32-trunk-686.bak /boot/System.map-2.6.32-trunk-686 /boot/vmlinuz-2.6.32-trunk-686Since they are stale files, not associated with any installed package, why not simply delete the files?Yes, that is one option. But how do I make sure I got all the stale files? If a package is known by apt, I can use "dpkg -L <package name" to see which files are installed and where. In this case, however, dpkg cannot tell me that.cruft can. Package: cruft State: not installed Version: 0.9.12 Priority: optional Section: admin Maintainer: Marcin Owsiany <porridge@debian.org> Uncompressed Size: 1,348k Depends: libc6 (>= 2.7-1), file Description: Find any cruft built up on your systemcruft is a program to look over your system for anything that shouldn't be there, but is; or for anything that should be there, but isn't. It bases most of its results on dpkg's database, as well as a list of `extra files' that can appear during the lifetime of various packages. cruft is still in pre-release; your assistance in improving its accuracy and performanceis appreciated. Homepage: http://alioth.debian.org/projects/cruft/
So I installed cruft and it produced a 24MB report. I don't even know how to look at that. And what means '---- missing USERS ----'?
Hugo