<div dir="ltr">Yes, there are a whole bunch:<br><br>rsm@rsm-laptop:~$ ls /boot<br>abi-2.6.32-24-generic config-2.6.32-33-generic System.map-2.6.24-21-eeepc vmcoreinfo-2.6.32-33-generic<br>abi-2.6.32-25-generic config-2.6.32-34-generic System.map-2.6.32-24-generic vmcoreinfo-2.6.32-34-generic<br>
abi-2.6.32-26-generic config-2.6.32-35-generic System.map-2.6.32-25-generic vmcoreinfo-2.6.32-35-generic<br>abi-2.6.32-27-generic config-2.6.32-37-generic System.map-2.6.32-26-generic vmcoreinfo-2.6.32-37-generic<br>
abi-2.6.32-28-generic config-2.6.32-41-generic System.map-2.6.32-27-generic vmcoreinfo-2.6.32-41-generic<br>abi-2.6.32-29-generic config-2.6.32-57-generic System.map-2.6.32-28-generic vmcoreinfo-2.6.32-57-generic<br>
abi-2.6.32-30-generic grub System.map-2.6.32-29-generic vmlinuz-2.6.24-21-eeepc<br>abi-2.6.32-31-generic initrd.img-2.6.24-21-eeepc System.map-2.6.32-30-generic vmlinuz-2.6.32-24-generic<br>
abi-2.6.32-32-generic initrd.img-2.6.24-21-eeepc.bak System.map-2.6.32-31-generic vmlinuz-2.6.32-25-generic<br>abi-2.6.32-33-generic initrd.img-2.6.32-24-generic System.map-2.6.32-32-generic vmlinuz-2.6.32-26-generic<br>
abi-2.6.32-34-generic initrd.img-2.6.32-25-generic System.map-2.6.32-33-generic vmlinuz-2.6.32-27-generic<br>abi-2.6.32-35-generic initrd.img-2.6.32-26-generic System.map-2.6.32-34-generic vmlinuz-2.6.32-28-generic<br>
abi-2.6.32-37-generic initrd.img-2.6.32-27-generic System.map-2.6.32-35-generic vmlinuz-2.6.32-29-generic<br>abi-2.6.32-41-generic initrd.img-2.6.32-28-generic System.map-2.6.32-37-generic vmlinuz-2.6.32-30-generic<br>
abi-2.6.32-57-generic initrd.img-2.6.32-29-generic System.map-2.6.32-41-generic vmlinuz-2.6.32-31-generic<br>config-2.6.24-21-eeepc initrd.img-2.6.32-30-generic System.map-2.6.32-57-generic vmlinuz-2.6.32-32-generic<br>
config-2.6.32-24-generic initrd.img-2.6.32-31-generic vmcoreinfo-2.6.32-24-generic vmlinuz-2.6.32-33-generic<br>config-2.6.32-25-generic initrd.img-2.6.32-32-generic vmcoreinfo-2.6.32-25-generic vmlinuz-2.6.32-34-generic<br>
config-2.6.32-26-generic initrd.img-2.6.32-33-generic vmcoreinfo-2.6.32-26-generic vmlinuz-2.6.32-35-generic<br>config-2.6.32-27-generic initrd.img-2.6.32-34-generic vmcoreinfo-2.6.32-27-generic vmlinuz-2.6.32-37-generic<br>
config-2.6.32-28-generic initrd.img-2.6.32-35-generic vmcoreinfo-2.6.32-28-generic vmlinuz-2.6.32-41-generic<br>config-2.6.32-29-generic initrd.img-2.6.32-37-generic vmcoreinfo-2.6.32-29-generic vmlinuz-2.6.32-57-generic<br>
config-2.6.32-30-generic initrd.img-2.6.32-41-generic vmcoreinfo-2.6.32-30-generic<br>config-2.6.32-31-generic initrd.img-2.6.32-57-generic vmcoreinfo-2.6.32-31-generic<br>config-2.6.32-32-generic memtest86+.bin vmcoreinfo-2.6.32-32-generic<br>
rsm@rsm-laptop:~$ <br><br><br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 29, 2014 at 2:39 PM, Nils Kassube <span dir="ltr"><<a href="mailto:kassube@gmx.net" target="_blank">kassube@gmx.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">Rick Magraw wrote:<br>
> I apologize if I am the culprit, and taking up some much time and<br>
> effort.<br>
<br>
</div>Np problem.<br>
<div class=""><br>
> I did redo (copy and paste) the ln command line, and have now gotten<br>
> back to the original error message about not enough disk space,<br>
> albeit now requiring a smaller amount ,i.e., 776 N on "/'<br>
><br>
> (I did not redo the mv command line).<br>
><br>
> Not enough free disk space<br>
> The upgrade has aborted.<br>
> The upgrade needs a total of 1,623 M of free space on disk '/'<br>
> Please free at least an additional space of 776 M on disk '/'<br>
> Empty your trash and remove temporary packages of former installations<br>
> using sudo apt- get clean.<br>
<br>
</div>Well, the suggested "apt- get clean" wouldn't help because the packages<br>
are on the other partition now. How many kernels are installed on that<br>
system? Maybe you should remove all but the currently used kernel and<br>
also the kernel-header for those kernels. That could free up enough<br>
space. You really only need one kernel because the new release will also<br>
install a new kernel. To find out what kernels may be obsolete, you can<br>
use the command<br>
<br>
ls /boot<br>
<br>
and if you need some help to find the appropriate command, please post<br>
the output of the command above.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
Nils<br>
<br>
<br>
<br>
<br>
--<br>
ubuntu-users mailing list<br>
<a href="mailto:ubuntu-users@lists.ubuntu.com">ubuntu-users@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-users" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-users</a><br>
</div></div></blockquote></div><br></div>