On 15 January 2015 at 14:49, Cláudio Sampaio <pat...@gmail.com> wrote: > On Thu, Jan 15, 2015 at 12:45 PM, Colin Law <clan...@gmail.com> wrote: >> >> On 15 January 2015 at 14:37, Dustin Kirkland <kirkl...@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 discussed. Nothing I have been posting should be taken to mean that I do not think an improvement to update-manger is desirable. Colin -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
