PDA

View Full Version : [server] 3.2 kernels on 14.04 LTS



MakOwner
December 30th, 2015, 03:08 PM
I just noticed while doing some house keeping that I have a couple of 14.04 LTS server installations with some 3.2 kernels.
Just the images, no headers.
The running kernel is 3.13.0-74.

Why would these be installed by normal 'apt-get update' operations?



rc linux-image-3.2.0-64-generic 3.2.0-64.97 amd64 Linux kernel image for version 3.2.0 on 64 bit x86 SMP
rc linux-image-3.2.0-65-generic 3.2.0-65.99 amd64 Linux kernel image for version 3.2.0 on 64 bit x86 SMP
rc linux-image-3.2.0-67-generic 3.2.0-67.101 amd64 Linux kernel image for version 3.2.0 on 64 bit x86 SMP
rc linux-image-3.2.0-68-generic 3.2.0-68.102 amd64 Linux kernel image for version 3.2.0 on 64 bit x86 SMP
rc linux-image-3.2.0-70-generic 3.2.0-70.105 amd64 Linux kernel image for version 3.2.0 on 64 bit x86 SMP
rc linux-image-3.2.0-72-generic 3.2.0-72.107 amd64 Linux kernel image for version 3.2.0 on 64 bit x86 SMP
rc linux-image-3.2.0-74-generic 3.2.0-74.109 amd64 Linux kernel image for version 3.2.0 on 64 bit x86 SMP
rc linux-image-3.2.0-75-generic 3.2.0-75.110 amd64 Linux kernel image for version 3.2.0 on 64 bit x86 SMP
ii linux-image-3.2.0-79-generic 3.2.0-79.115 amd64 Linux kernel image for version 3.2.0 on 64 bit x86 SMP

deadflowr
December 30th, 2015, 06:52 PM
You only actually have one 3.2 kernel (3.2.0-79)
the rest are uninstalled, but have leftover residual configuration files.
(most likely documentation files; I've seen these in /usr/share/doc before)

You can try the autoremove command to see if the lone 3.2 kernel will be removed

sudo apt-get autoremove
note that the above will still leave those residual packages.

Here's something I've done once upon a time to clear those out with.
First run this to get a breakdown of the deinstalled linux packages:

dpkg --get-selections | grep deinstall | grep -E linux
now add another pipe to run it through awk so as to cut out the deinstall entry

dpkg --get-selections | grep deinstall | grep -E linux | awk '{print $1}'
then and another pipe and use xargs to apt-get purge those entries, but first run it with an -s option to simulate the action.

dpkg --get-selections | grep deinstall | grep -E linux | awk '{print $1}' | xargs sudo apt-get purge -s
review the output to make sure nothing but those linux packages you wanted to remove are gone.
Then if it looks all right, remove that -s option; replace it with -y, and go for it.

Hope it helps

ubfan1
December 30th, 2015, 08:02 PM
You probably upgraded from the 12.04 release, which used the 3.2 kernel series, and have some leftovers.
I manually remove old kernels, using just the number, which seems to be enough to specify the needed packages:
apt-cache pkgnames |grep 3.2.0-79
Ensure all the kernel packages (more than you have really installed but no problem)
Then if the list is OK, on the very next command type:
sudo apt-get purge `!!`
To recall the previous list of packages for purging.
You will be given another reconfirm message to accept before the actual purge.

MakOwner
December 31st, 2015, 02:05 AM
So I'm not the only one seeing this - that alleviates some of my concern.
This is a 64bit 14.0 LTS server install with release-upgrade through to 14.04.

I have removed all of the 3.2 kernel packages and using apt-get purge on a test server and everything seems to still function.