4 ms·

It's user error on your part. The proper way to upgrade a Debian/Ubuntu system is: $ apt-get dist-upgrade $ apt-get autoremove dist-upgrade installs new k

by mrb 10y ago

It's user error on your part. The proper way to upgrade a Debian/Ubuntu system is: $ apt-get dist-upgrade $ apt-get autoremove dist-upgrade installs new kernels, and autoremove will automatically remove old kernels (and keep the last 2 most recent ones.)

edoloughlin 10y ago
autoremove followed by dist-upgrade to 16.04 for me somehow decided to build multiple kernel versions and ran out of space on /boot mid build. That was really annoying to fix.
- mrb 10y ago
  Run autoremove after dist-upgrade.
- blacksmith_tb 10y ago
  dist-upgrade shouldn't try and move you to another release version, do-release-upgrade alone does that, as far as I know. Things get a little more confusing using apt update/upgrade vs. apt-get update/dist-upgrade, they don't seem to be quite the same in all cases for me. But I agree with the general frustration that it shouldn't be necessary to run apt(-get) autoremove frequently to keep /boot from filling up with old kernels.
- mrb 10y ago
  There is a lot of confusion in this thread. dist-upgrade is NOT (in most cases) meant to upgrade to a newer distribution (eg. Ubuntu 14.04 to 16.04). dist-upgrade is just like upgrade except it also installs additional packages if necessary (eg. linux-kernel-4.1 AND linux-kernel-4.2). Most people should always run "apt-get dist-upgrade" and never "apt-get upgrade" in order to simply keep their packages up-to-date. An actual distribution upgrade is triggered by a different command. On Ubuntu: do-release-upgrade
lathiat 10y ago
I like to use apt-get dist-upgrade --auto-remove, all in one step. Though for kernels they will be removed on the next invocation after reboot as the default logic keeps the last installed kernel version as well as the current one. As for the original issue of not cleaning up the kernels, this is fixed in xenial/16.04 but not in trusty/14.04, see bug report here: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1439769 https://bugs.launchpad.net/ubuntu/+source/update-manager/+bu...
- nightsky30 10y ago
  Xenial/16.04 has other issues regarding kernel cleanup involving DKMS leaving files behind: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717584 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717584 https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513 https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513

by mrb 10y ago

edoloughlin 10y ago

autoremove followed by dist-upgrade to 16.04 for me somehow decided to build multiple kernel versions and ran out of space on /boot mid build. That was really annoying to fix.

mrb 10y ago
Run autoremove after dist-upgrade.
blacksmith_tb 10y ago
dist-upgrade shouldn't try and move you to another release version, do-release-upgrade alone does that, as far as I know. Things get a little more confusing using apt update/upgrade vs. apt-get update/dist-upgrade, they don't seem to be quite the same in all cases for me. But I agree with the general frustration that it shouldn't be necessary to run apt(-get) autoremove frequently to keep /boot from filling up with old kernels.
mrb 10y ago
There is a lot of confusion in this thread. dist-upgrade is NOT (in most cases) meant to upgrade to a newer distribution (eg. Ubuntu 14.04 to 16.04). dist-upgrade is just like upgrade except it also installs additional packages if necessary (eg. linux-kernel-4.1 AND linux-kernel-4.2). Most people should always run "apt-get dist-upgrade" and never "apt-get upgrade" in order to simply keep their packages up-to-date. An actual distribution upgrade is triggered by a different command. On Ubuntu: do-release-upgrade

lathiat 10y ago

I like to use apt-get dist-upgrade --auto-remove, all in one step. Though for kernels they will be removed on the next invocation after reboot as the default logic keeps the last installed kernel version as well as the current one. As for the original issue of not cleaning up the kernels, this is fixed in xenial/16.04 but not in trusty/14.04, see bug report here: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1439769 https://bugs.launchpad.net/ubuntu/+source/update-manager/+bu...

nightsky30 10y ago
Xenial/16.04 has other issues regarding kernel cleanup involving DKMS leaving files behind: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717584 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717584 https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513 https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513