Description of Problem: new-kernel-pkg does not check mkinitrd success and may leave system unbootable if mkinitrd fails. How Reproducible: always. Steps to Reproduce: 1. mount /tmp on /dev/shm from /etc/fstab: /dev/shm /tmp tmpfs bind 0 0 2. install (do not upgrade) new kernel 3. ls /boot to check if there is new initrd Actual Results: no new initrd created because losetup fails on /dev/shm Expected Results: new-kernel-pkg a least reports an error to user....
good point... new-kernel-pkg will no longer run grubby if mkinitrd returns an error
More potential problems, please comment. Should mkinitrd query temporary filesystem type before it runs losetup on it? Since mkinitrd always (?) runs as root would be more appropriate to use $HOME or ~ for temporary files if losetup on /tmp or /var/tmp fails? Another question: What will happen if new-kernel-pkg will not run grubby but user typed rpm -U kernel-x.x.x ? Will new-kernel-pkg tell rpm that upgrade failed and old package can not be erased?