Updater can't update kernel due to disk space

Colin Law clanlaw at gmail.com
Thu Jan 15 14:58:08 UTC 2015

On 15 January 2015 at 14:49, Cláudio Sampaio <patola at gmail.com> wrote:
> On Thu, Jan 15, 2015 at 12:45 PM, Colin Law <clanlaw at gmail.com> wrote:
>> On 15 January 2015 at 14:37, Dustin Kirkland <kirkland at canonical.com>
>> wrote:
>> > ...
>> > I have Ubuntu Server instances in the Cloud, with very tiny root disks,
>> > one
>> > of which has run for several years, autoupdating, and accumulated 37(!!)
>> > kernels, which filled up its 8GB root partition.
>> >
>> > Around that time a few years ago, I wrote the "purge-old-kernels"
>> > command
>> > (http://manpg.es/purge-old-kernels), which does a very effective job of
>> > saving your current kernel, and one other known working kernel, while
>> > deleting the rest.  I was working on getting that into the distro (and
>> > out
>> > of the bikeshed package), but Adam Conrad told me that apt would fix
>> > this,
>> > itself.  I've CC'd Adam.  Can you advise us, Adam?
>> As from 14.04 apt-get autoremove should remove old kernels except for
>> current and most recent.
> apt-get autoremove is an "arcane command-line tool". I thought by this part
> of the discussion it had became clear that it is not a sensible solution
> (except maybe if auto-scheduled).

It seemed to me that Dustin was not aware of using autoremove,
otherwise why tell us about his purge-old-kernels script, since that
function is now handled by autoremove?   Also, since he is talking
about a server no change to the update-manager gui app is going to be
relevant.  I thought from the OP that this was what was being

Nothing I have been posting should be taken to mean that I do not
think an improvement to update-manger is desirable.


More information about the Ubuntu-devel-discuss mailing list