Description of problem: Request for more robust kernel .rpm file. Today, an upgrade of the kernel-package on a system with read-only /boot partition, renders the system unbootable. You can successfully (according to yum) install the kernel package on such a read-only /boot. It will update the grub.conf and next boot it won't find the non-installed kernel (when using the default grub choice) --> can't startup. Version-Release number of selected component (if applicable): kernel (all) How reproducible: always when kernel update available Steps to Reproduce: 1. mount /boot as read-only 2. yum update kernel 3. Actual results: $ yum update kernel <snip> Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing: kernel ######################### [1/1] error: unpacking of archive failed on file /boot/System.map-2.6.22.4-65.fc7;46cfe671: cpio: open Installed: kernel.x86_64 0:2.6.22.4-65.fc7 Complete! Expected results: I would expect the package to check if /boot is writable, if no, a transaction check error and a failure of the package update. Additional info:
> You can successfully (according to yum) That would suggest a yum bug, not a kernel bug. > install the kernel package on such a > read-only /boot. It will update the grub.conf and next boot it won't find the > non-installed kernel (when using the default grub choice) --> can't startup. Erm, grub.conf is on /boot so how would it have been updated if /boot was read-only?
This is a dupe of bug 186945 except that's against devel and this for F7 - yum can catch this error if it wants to and IIRC yum 3.2.3 already does.
*** This bug has been marked as a duplicate of 186945 ***