On 19 June 2013 23:39, Daniel Hartwig <email address hidden> wrote:
> On 19 June 2013 09:41, Gary Shook <email address hidden> wrote:
>> I cleaned it up using the following:
>> dpkg -l linux-* | awk '/^ii/{ print $2}' | grep -v -e `uname -r | cut -f1,2
>> -d"-"` | grep -e [0-9] | xargs sudo apt-get -y purge
>>
>> I donn't have the output before cleanup, but I can tell you it was a bunch
>> of old kernel images.
>>
>
> In previous versions old kernal images would not be subject to
> automatical removal by default, that was changed recently. It is
> possible that these old kernal images were installed before the
> change, and as such required to be cleaned up manually. That being
> the case the issue should not recur, and please let us know if it does
> so that we can track down the cause.
>
status invalid
As said, please reopen if the problem recurs and we can attempt to
track it down. Remember to obtain the requested information before
you repair the system.
On 19 June 2013 23:39, Daniel Hartwig <email address hidden> wrote:
> On 19 June 2013 09:41, Gary Shook <email address hidden> wrote:
>> I cleaned it up using the following:
>> dpkg -l linux-* | awk '/^ii/{ print $2}' | grep -v -e `uname -r | cut -f1,2
>> -d"-"` | grep -e [0-9] | xargs sudo apt-get -y purge
>>
>> I donn't have the output before cleanup, but I can tell you it was a bunch
>> of old kernel images.
>>
>
> In previous versions old kernal images would not be subject to
> automatical removal by default, that was changed recently. It is
> possible that these old kernal images were installed before the
> change, and as such required to be cleaned up manually. That being
> the case the issue should not recur, and please let us know if it does
> so that we can track down the cause.
>
status invalid
As said, please reopen if the problem recurs and we can attempt to
track it down. Remember to obtain the requested information before
you repair the system.
Thanks