touch-packages team mailing list archive

[Gordon <kmputerguy@xxxxxxxxx>]

When I installed 14.04 server it gave me the option to automatically
install updates.  I picked yes.  I logged in a year later to find that
my servers had installed three updates, then ran into this bug and
stopped.  In fact, kernel updates come out so often that half the time I
try to install software apt is in a broken state because of this.

I could almost understand this kind of behaviour if having a cronjob do
apt-get upgrade was a non-standard setup, but if it's an option in the
installer?  Unacceptable, and stupid.

A bug that completely breaks all security updates *should* be considered
a security bug.  If Microsoft made the same mistake we'd lose no time in
mocking them for their insecure OS.  Why should we hold ourselves to a
different standard?


My suggestion for a fix would be to fix apt-get autoremove to skip the current running kernel.  That way, autoremove can be triggered automatically right after update without worrying about screwing up the currently running kernel.

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

Title:
  /boot fills up after many kernel upgrades

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  THIS ISSUE MAY PREVENT SECURITY UPDATES TO THE KERNEL.

  Obsolete versions of the kernel remain installed on a system, causing a full /boot or wasting space on single-partition installations.
  This has the effect that (some) software updates no longer work (at least those to the kernel):

  update-initramfs: Generating /boot/initrd.img-3.2.0-29-generic

  gzip: stdout: No space left on device
  [...]
  Errors were encountered while processing:
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  To resolve this, the user must figure out which packages to deinstall.
  A novice user will not know what to do.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1037285/+subscriptions