Description of problem: While applying 20070926 updates I got never seen before message: Cleanup : kernel ##################### [229/316] ls: cannot access /boot/initrd*kdump.img: No such file or directory Apparently something tries to use 'ls' to check an existence of a file with name pattern of "/boot/initrd*kdump.img". This is an obviously wrong approach but I cannot figure out which of kernel installation tools does something like that. It does not look like directly kernel package scripts so something called there. Ideas?
something broke in new-kernel-pkg maybe? Peter ?
I found what is broken. While removing some kernel with 'rpm -evv ...': .... D: erase: %postun(kexec-tools-1.102pre-1.fc8.x86_64) asynchronous scriptlet start D: erase: %trigger(kexec-tools-1.102pre-1.fc8.x86_64) execv(/bin/sh) pid 10916 ++ ls '/boot/initrd*kdump.img' ls: cannot access /boot/initrd*kdump.img: No such file or directory ..... and 'rpm -q --triggers kexec-tools' shows #start by getting a list of all the kdump initrds for i in `ls /boot/initrd*kdump.img` do KDVER=`echo $i | sed -e's/^.*initrd-//' -e's/kdump.*$//'` .... done That is clearly wrong. That loop should read for i in /boot/initrd*kdump.img ; do [ -e "$i" ] || continue KDVER=`echo $i | sed -e's/^.*initrd-//' -e's/kdump.*$//'` .... done unless you want to use 'shopt -s nullglob' and make an existence test redundant. Setting KDVER also does not require external programs. KDVER="${i##*initrd-}" ; KDVER="${KDVER%%kdump*}" The abvove with kexec-tools-1.102pre-1.fc8.
Yep you're right. Thanks for the catch. Commited to the fedora devel branch. Thanks!