I have not used fedup, but it is quite possible that your boot partition
has copies of several kernels. This can happen if you have been running
system updates as they come up.
Each time the kernel gets updated, it keeps a copy of the previous
kernel, just in case.
If you look in your /boot directory, you are likely to see something
like this, with three of initramfs, vmlinuz, System.map etc;
$ ls -laSh /boot
total 115M
-rw-------. 1 root root 38M Jan 9 2014
initramfs-0-rescue-19a1b60a7cf54849924a3116ee2515bc.img
-rw------- 1 root root 16M Jul 18 12:20
initramfs-3.15.5-200.fc20.x86_64.img
-rw------- 1 root root 16M Aug 1 17:53
initramfs-3.15.7-200.fc20.x86_64.img
-rw------- 1 root root 16M Jul 4 07:44
initramfs-3.14.9-200.fc20.x86_64.img
-rwxr-xr-x 1 root root 5.3M Jul 29 04:59 vmlinuz-3.15.7-200.fc20.x86_64
-rwxr-xr-x 1 root root 5.3M Jul 15 01:49 vmlinuz-3.15.5-200.fc20.x86_64
-rwxr-xr-x 1 root root 5.3M Jun 27 07:51 vmlinuz-3.14.9-200.fc20.x86_64
-rwxr-xr-x. 1 root root 5.0M Jan 9 2014
vmlinuz-0-rescue-19a1b60a7cf54849924a3116ee2515bc
-rw------- 1 root root 2.8M Jul 29 04:59 System.map-3.15.7-200.fc20.x86_64
-rw------- 1 root root 2.8M Jul 15 01:49 System.map-3.15.5-200.fc20.x86_64
-rw------- 1 root root 2.8M Jun 27 07:51 System.map-3.14.9-200.fc20.x86_64
-rw-r--r--. 1 root root 572K Dec 12 2013 initrd-plymouth.img
-rw-r--r-- 1 root root 193K Apr 4 02:57 elf-memtest86+-5.01
-rw-r--r-- 1 root root 191K Apr 4 02:57 memtest86+-5.01
-rw-r--r-- 1 root root 140K Jul 29 04:59 config-3.15.7-200.fc20.x86_64
-rw-r--r-- 1 root root 140K Jul 15 01:49 config-3.15.5-200.fc20.x86_64
-rw-r--r-- 1 root root 139K Jun 27 07:51 config-3.14.9-200.fc20.x86_64
drwx------. 2 root root 12K Jan 9 2014 lost+found
drwxr-xr-x. 20 root root 4.0K Aug 2 07:23 ..
dr-xr-xr-x. 6 root root 3.0K Aug 1 17:53 .
drwxr-xr-x. 4 root root 1.0K Dec 12 2013 efi
drwxr-xr-x. 2 root root 1.0K Dec 12 2013 extlinux
drwxr-xr-x. 6 root root 1.0K Aug 1 17:53 grub2
-rw-r--r-- 1 root root 167 Jun 27 07:51
.vmlinuz-3.14.9-200.fc20.x86_64.hmac
-rw-r--r-- 1 root root 167 Jul 15 01:49
.vmlinuz-3.15.5-200.fc20.x86_64.hmac
-rw-r--r-- 1 root root 167 Jul 29 04:59
.vmlinuz-3.15.7-200.fc20.x86_64.hmac
If you now look at your grub config in /boot/grub2/grub.conf, you will
see three or fur grub menu items which match the files above. If you
delete the files which match the the menu entries except menu entry #1,
it might free up enough space for your upgrade.
Incidentally, on my computer the boot partition (as automatically set up
by the installer is 500 MB with 145 MB used.
Hope this helps
On 03/08/14 13:49, Richard Vickery wrote:
The problem is that I am prevented from ungrading through fedup because there is not enough space in /boot
Richard
_______________________________________________
laptop mailing list
laptop@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/laptop
