Hi Jarno

I would suggest that most desktop users get notified by the updater that
there are updates and run the updater accordingly to apply them.  As
such, I think the unclogging activity needs to run  automatically as the
users that are using the default boot partition size almost certainly
have no interest in having to run the software themselves or even making
a decision about how many old kernels to keep. In fact I suggest that
there are a goodly number of users that wouldn't know what to do with an
old kernel anyway.

My suggestion would be that there should be a default number of kernels
to keep (2 or maybe 3 would be my vote) but have a configuration file
that would allow the number to be altered for those users that wanted to
change the default. In fact you could even use a 0 value to indicate
that the user does not want the un-clogging to happen automatically.

It seems like all the commands and scripts have been sorted out over
time and the work is really to apply them in an automated fashion. I do
recognise that, there may be a more elegant solution that might be
preferable though.  In which case that is going to be more work.

If we are talking about putting this in place to run automatically and
definitely removing the "out of space" issue with no effort on behalf of
the user, then I would be happy to contribute towards the bounty.  Can
you confirm that this would be the intention?

I don't think that the default size of the boot partition should be
ignored though.  Surely it's not going to break anyone's system to up
the size to 500Mb.  Whilst I'm not a developer, I can't believe it would
take much effort to increase the default size.

Thanks for your persistence and help moving this bug along Jarno.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to