Hi Jarno,

Thanks for all your advice and additional thanks to *Pxtl* for the idea of
a script, here's my own variation...

```
sudo apt-get purge `dpkg -l "linux-image-3.13.0-8*" | grep -E
"linux-image-3.13.0-8*" | awk {'print $2'} | tr '\n' ' '`
```

*Explaination*:  the *dpkg* lists all the kernel images, followed by *grep*
to limit the list to just version .8* kernels and lastly *awk* and *tr*
convert the vertical list into a one-liner that is encapsulated by back
ticks that wraps into an *apt-get purge* command with a chance to review
everything before committing to Yes, use caution...

This freed up my */boot* volume, here's before and after running it over
version .7* and .8* kernels using *df -h*

/dev/sda1                               236M  187M   37M  84% /boot  --
BEFORE

/dev/sda1                               236M   70M  154M  31% /boot  --
AFTER

Finally my installed kernels as of now...

linux-image-3.13.0-24-lowlatency
linux-image-3.13.0-91-generic
linux-image-3.13.0-91-lowlatency
linux-image-3.13.0-92-generic
linux-image-3.13.0-92-lowlatency
linux-image-extra-3.13.0-77-generic
linux-image-extra-3.13.0-79-generic
linux-image-extra-3.13.0-83-generic
linux-image-extra-3.13.0-86-generic
linux-image-extra-3.13.0-87-generic
linux-image-extra-3.13.0-88-generic
linux-image-extra-3.13.0-91-generic
linux-image-extra-3.13.0-92-generic
linux-image-generic
linux-image-generic-lts-trusty
linux-image-lowlatency

It appears as if *apt-get purge* properly sorted out which *lowlatency* and
which *generic* kernels to keep.
I'd suggest this a potential workaround for now, please test and verify.
Many thanks in advance.

Kind Regards,
Gordon


On Sun, Jul 24, 2016 at 6:01 AM, Jarno Suni <email address hidden>
wrote:

> Alan Burgess, have you tried to follow the workaround given in the
> description to manually remove old kernels and to setup automatic
> removal of old kernels?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/798414
>
> Title:
>   update-initramfs should produce a more helpful error when there isn't
>   enough  free space
>
> Status in initramfs-tools:
>   Confirmed
> Status in initramfs-tools package in Ubuntu:
>   In Progress
>
> Bug description:
>   Binary package hint: initramfs-tools
>
>   When generating a new initramfs there is no check for available free
>   space, subsequently its possible for update-initramfs to fail due to a
>   lack of free space.  This is resulting in package installation
>   failures for initramfs-tools.  For example:
>
>   Setting up initramfs-tools (0.98.8ubuntu3) ...
>   update-initramfs: deferring update (trigger activated)
>   Processing triggers for initramfs-tools ...
>   update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic
>
>   gzip: stdout: No space left on device
>   E: mkinitramfs failure cpio 141 gzip 1
>   update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
>   dpkg: error processing initramfs-tools (--configure):
>    subprocess installed post-installation script returned error exit
> status 1
>
>   WORKAROUND:
>
>   Remove unused kernels using computer janitor (not in repositories for
>   14.04 or later) or manually free space on your partition containing
>   the /boot file system.
>
>   See instructions here
>   https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions
>