On 30 June 2013 04:28, Redoubts redou...@gmail.com wrote:
To confuse matters, the kernel images include apparently more recent
images: 3.5.0-28-generic ..
Technically, that's the older kernel from Ubuntu 12.10; note the 3.5, vs
3.8 for others.
Regarding your rhetorical part, we should also
On 19 June 2013 23:39, Daniel Hartwig mand...@gmail.com wrote:
On 19 June 2013 09:41, Gary Shook garyfsh...@gmail.com 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
On 19 June 2013 09:41, Gary Shook garyfsh...@gmail.com 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
On 19 June 2013 14:30, Michael McAndrew 1191...@bugs.launchpad.net wrote:
I then rebooted and did an 'ls -lR /boot' and a 'sudo aptitude-upgrade'
As you are using aptitude to upgrade old kernel images will not be
automatically removed (bug #923876). Those should be removed manually
to free up
I do not use aptitude, and do not have unattended-upgrades installed.
at this point, I get a system error on boot, and just need to fix it... I
cleaned up /boot it had no space left.
I need to improve my boot maintenance.
here is the output after cleanup:
/boot:
total 39614
-rw-r--r-- 1 root
On 19/06/2013 8:51 AM, Gary Shook garyfsh...@gmail.com wrote:
I do not use aptitude, and do not have unattended-upgrades installed.
at this point, I get a system error on boot, and just need to fix it... I
cleaned up /boot it had no space left.
How did you clean it up, by removing files or
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.
my system works, but I'm getting a