trying to understand/purge linux-image-2.6.32-trunk-686
in [Debian]
|
From: H.S. on 1 Jun 2010 13:30 There was a slight screw-up with my mount points of /boot earlier today, when I was doing a bit of house cleaning. I purged some old kernels and installed a new one while /boot was mounted on a different partition (another story, sigh!). I noticed the problems and fixed that and rebooted with proper mounting. This, of course, resulted in the kernel files still in (correct) /boot that were supposed to have been purged. To fix that, with /boot correctly mounted, I reinstalled the kernel packages that I had purged and then purged them. 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 However, I am not sure to which package this belongs: $> dpkg -l linux-image-2\.6\.32* | grep trunk un linux-image-2.6.32-trunk-686 <none> (no description available) If that is its package, apt can't find it: $> apt-cache show linux-image-2.6.32-trunk-686 W: Unable to locate package linux-image-2.6.32-trunk-686 E: No packages found Anybody know what is the deal with this kernel image? What am I missing here? 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/hu3g10$4a9$1(a)dough.gmane.org
From: Hugo Vanwoerkom on 2 Jun 2010 09:50 H.S. wrote: > There was a slight screw-up with my mount points of /boot earlier today, > when I was doing a bit of house cleaning. I purged some old kernels and > installed a new one while /boot was mounted on a different partition > (another story, sigh!). I noticed the problems and fixed that and > rebooted with proper mounting. This, of course, resulted in the kernel > files still in (correct) /boot that were supposed to have been purged. > To fix that, with /boot correctly mounted, I reinstalled the kernel > packages that I had purged and then purged them. > > 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 > > > However, I am not sure to which package this belongs: > $> dpkg -l linux-image-2\.6\.32* | grep trunk > un linux-image-2.6.32-trunk-686 <none> (no description available) > > If that is its package, apt can't find it: > $> apt-cache show linux-image-2.6.32-trunk-686 > W: Unable to locate package linux-image-2.6.32-trunk-686 > E: No packages found > > > Anybody know what is the deal with this kernel image? What am I missing > here? > What about 'dpkg -P 2.6.32-trunk-686'? 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/hu5ndi$bug$1(a)dough.gmane.org
From: H.S. on 2 Jun 2010 11:20 On 02/06/10 09:47 AM, Hugo Vanwoerkom 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 >> >> >> However, I am not sure to which package this belongs: >> $> dpkg -l linux-image-2\.6\.32* | grep trunk >> un linux-image-2.6.32-trunk-686 <none> (no description available) >> >> If that is its package, apt can't find it: >> $> apt-cache show linux-image-2.6.32-trunk-686 >> W: Unable to locate package linux-image-2.6.32-trunk-686 >> E: No packages found >> >> >> Anybody know what is the deal with this kernel image? What am I missing >> here? >> > > What about 'dpkg -P 2.6.32-trunk-686'? > It is already being shown as not installed. In fact, I am trying to install it. The problem with this kernel is that I purged it when /boot was mistakenly mounted on some other device. So apt worked as far as its database is concerned, but the package's files remained on the original /boot. Now that I have the correct boot, I would like to install the package again and then follow by purging it so that aptitude now removes all the files from the correct /boot. -- 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/hu5s8i$k2$1(a)dough.gmane.org
From: Tom Furie on 2 Jun 2010 11:30 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 > >> > The problem with this kernel is that I purged it when /boot was > mistakenly mounted on some other device. So apt worked as far as its > database is concerned, but the package's files remained on the original > /boot. Now that I have the correct boot, I would like to install the > package again and then follow by purging it so that aptitude now removes > all the files from the correct /boot. Since they are stale files, not associated with any installed package, why not simply delete the files? Cheers, Tom -- What you don't know won't help you much either. -- D. Bennett
From: H.S. on 2 Jun 2010 11:50 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. -- 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/hu5uee$94o$1(a)dough.gmane.org
|
Next
|
Last
Pages: 1 2 3 Prev: Votre ipad -90% Next: SuperGrubDisk (was: businesscard CD as rescue CD Tutorial?) |