trying to understand/purge linux-image-2.6.32-trunk-686
in [Debian]
|
From: Boyd Stephen Smith Jr. on 2 Jun 2010 12:00 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-686 > > > > Since 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(a)debian.org> Uncompressed Size: 1,348k Depends: libc6 (>= 2.7-1), file Description: Find any cruft built up on your system cruft 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 performance is appreciated. Homepage: http://alioth.debian.org/projects/cruft/ -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss(a)iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
From: Tom Furie on 2 Jun 2010 12:40 On Wed, Jun 02, 2010 at 11:47:26AM -0400, H.S. wrote: > On 02/06/10 11:19 AM, Tom Furie wrote: > > Since 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. As far as I can tell, generally linux-image* puts files in /lib/modules, /boot, /usr/share/doc, and /usr/share/bug. Now given that -trunk should never have made it to the repo's there may or may not be other files to find, but that should be a good start, and as mentioned in another reply, cruft might be able to help with any others. Cheers, Tom -- Frankfort, Kentucky, makes it against the law to shoot off a policeman's tie.
From: H.S. on 2 Jun 2010 13:00 On 02/06/10 11:50 AM, 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/vmlinuz-2.6.32-trunk-686 >>> >>> Since 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. > I tried cruft on my /boot partition and got more than I bargained for. It listed the files related to the package in question and some others too. They are: /boot/System.map-2.6.32-trunk-686 /boot/config-2.6.32-trunk-686 /boot/initrd.img-2.6.17-2-486.bak /boot/initrd.img-2.6.26-2-686 /boot/initrd.img-2.6.26-2-686.bak /boot/initrd.img-2.6.32-3-686 /boot/initrd.img-2.6.32-trunk-686 /boot/initrd.img-2.6.32-trunk-686.bak /boot/vmlinuz-2.6.32-trunk-686 I understand the files with 'trunk' in them, but the rest I am not why they are there since I have the following kernels installed: $> dpkg -l linux-image* | grep ^i | awk '{print $2}' linux-image-2.6-686 linux-image-2.6.26-2-686 linux-image-2.6.32-3-686 linux-image-686 And besides these, cruft also listed tons of /boot/grub files as unexplained. -- Please reply to this list only. I read this list on its corresponding newsgroup on gmane.org. Replies sent to my email address are just filtered to a folder in my mailbox and get periodically deleted without ever having been read. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/hu62es$pau$1(a)dough.gmane.org
From: Hugo Vanwoerkom on 2 Jun 2010 13:10 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-686 >>> Since 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(a)debian.org> > Uncompressed Size: 1,348k > Depends: libc6 (>= 2.7-1), file > Description: Find any cruft built up on your system > cruft 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 > performance > is 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 -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/hu635g$rns$1(a)dough.gmane.org
From: H.S. on 2 Jun 2010 13:20 On 02/06/10 12:36 PM, Tom Furie wrote: > On Wed, Jun 02, 2010 at 11:47:26AM -0400, H.S. wrote: >> On 02/06/10 11:19 AM, Tom Furie wrote: > >>> Since 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. > > As far as I can tell, generally linux-image* puts files in /lib/modules, > /boot, /usr/share/doc, and /usr/share/bug. Now given that -trunk should I have tried "dpkg -L" with installed kernels to see where they usually install files. So if push comes to shove, I can manually delete "trunk" kernel related files. I would be great to do this dpkg-way, however. Thanks. -- Please reply to this list only. I read this list on its corresponding newsgroup on gmane.org. Replies sent to my email address are just filtered to a folder in my mailbox and get periodically deleted without ever having been read. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/hu638u$sao$1(a)dough.gmane.org
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 Prev: Votre ipad -90% Next: SuperGrubDisk (was: businesscard CD as rescue CD Tutorial?) |