On Wed, 2 Jun 2010, Virgil wrote: > Just yum updated the kernel (probably should have installed as it turns out). It fails to do the initrd thing. > I've tried a force install to capture the error messages. yum should leave a few kernels (3 typically including the one you are running on) so you should be okay. > There was one other error message relating to plymouth not having a default. > I used `plymouth-set-default-theme text` to fix that. > > My running test system probably won't reboot now I'm guessing, so I hope the power doesn't go out :-) > > [root@seanl64 tmp]# rpm -ivh --force kernel-2.6.32.14-1.2.105.xendom0.fc12.x86_64.rpm rpm -ivh should be safe as the existing kernels will still be there (rpm -q kernel will list them), you just need to make sure you pick one of the other options at the boot menu. > Preparing... ########################################### [100%] > 1:kernel ########################################### [100%] > ln: creating symbolic link `libc.so.6' -> `': No such file or directory > ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or directory I am not sure about that - it looks like the initramfs build is failing. Are you short of free disk space (on /boot or more generally)? It would also be useful to know what errors rpm gives if you don't use the --force option and what Fedora version you are using. Michael Young -- xen mailing list xen@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/xen
