oh my
September 4th, 2010, 02:05 PM
Hi,
I have an issue with apt-get that has been bugging me, namely that it tries to delete kernels I did not specify for deletion.
This is an issue that has been present over at least the last three releases and is present for both 32bit and 64bit, so it might actually be a feature and not a bug, however I can't see it's usefulness.
When I use the command:
sudo apt-get remove --purge 2.6.32-21*It not only tries to remove the kernel 2.6.32.21 but gives me the following output:
sudo apt-get remove --purge 2.6.32-22*
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting linux-headers-lbm-2.6.32-24-generic for regex '2.6.32-22*'
Note, selecting linux-headers-2.6.32-21-preempt for regex '2.6.32-22*'
Note, selecting linux-backports-modules-alsa-2.6.32-21-generic for regex '2.6.32-22*'
Note, selecting linux-backports-modules-wireless-2.6.32-22-server for regex '2.6.32-22*'
[....]
shortened
[....]
Note, selecting linux-image-2.6.32-24-generic-pae for regex '2.6.32-22*'
Note, selecting linux-headers-2.6.32-23-generic for regex '2.6.32-22*'
The following packages will be REMOVED:
linux-generic* linux-headers-2.6.32-22* linux-headers-2.6.32-22-generic* linux-headers-2.6.32-23*
linux-headers-2.6.32-23-generic* linux-headers-2.6.32-24* linux-headers-2.6.32-24-generic*
linux-headers-generic* linux-image-2.6.32-22-generic* linux-image-2.6.32-23-generic*
linux-image-2.6.32-24-generic* linux-image-generic*
0 upgraded, 0 newly installed, 12 to remove and 0 not upgraded.
After this operation, 637MB disk space will be freed.
Do you want to continue [Y/n]?
I shortened the log. Full log here: http://pastebin.com/jCBExTka
Meaning it is happily trying to delete the specified kernel 2.6.32.22, but also the kernels 2.6.32.23, 2.6.32.21 and my current and latest kernel 2.6.32.24.
When I go through with this command to remove the oldest kernel on the system, it will actually delete all kernels present on my PC (as I painfully learned when I first tried it). Why is that the case? Wouldn't it make more sense to only remove the kernel 2.6.32.22?
regards oh my
I have an issue with apt-get that has been bugging me, namely that it tries to delete kernels I did not specify for deletion.
This is an issue that has been present over at least the last three releases and is present for both 32bit and 64bit, so it might actually be a feature and not a bug, however I can't see it's usefulness.
When I use the command:
sudo apt-get remove --purge 2.6.32-21*It not only tries to remove the kernel 2.6.32.21 but gives me the following output:
sudo apt-get remove --purge 2.6.32-22*
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting linux-headers-lbm-2.6.32-24-generic for regex '2.6.32-22*'
Note, selecting linux-headers-2.6.32-21-preempt for regex '2.6.32-22*'
Note, selecting linux-backports-modules-alsa-2.6.32-21-generic for regex '2.6.32-22*'
Note, selecting linux-backports-modules-wireless-2.6.32-22-server for regex '2.6.32-22*'
[....]
shortened
[....]
Note, selecting linux-image-2.6.32-24-generic-pae for regex '2.6.32-22*'
Note, selecting linux-headers-2.6.32-23-generic for regex '2.6.32-22*'
The following packages will be REMOVED:
linux-generic* linux-headers-2.6.32-22* linux-headers-2.6.32-22-generic* linux-headers-2.6.32-23*
linux-headers-2.6.32-23-generic* linux-headers-2.6.32-24* linux-headers-2.6.32-24-generic*
linux-headers-generic* linux-image-2.6.32-22-generic* linux-image-2.6.32-23-generic*
linux-image-2.6.32-24-generic* linux-image-generic*
0 upgraded, 0 newly installed, 12 to remove and 0 not upgraded.
After this operation, 637MB disk space will be freed.
Do you want to continue [Y/n]?
I shortened the log. Full log here: http://pastebin.com/jCBExTka
Meaning it is happily trying to delete the specified kernel 2.6.32.22, but also the kernels 2.6.32.23, 2.6.32.21 and my current and latest kernel 2.6.32.24.
When I go through with this command to remove the oldest kernel on the system, it will actually delete all kernels present on my PC (as I painfully learned when I first tried it). Why is that the case? Wouldn't it make more sense to only remove the kernel 2.6.32.22?
regards oh my