On Wed, 2010-05-19 at 18:11 -0400, C Linus Hicks wrote: > On Mon, 2010-05-17 at 01:20 -0400, JohnS wrote: > > I am just wondering if any of you guys with the udev hang problem have > > tried: > > rpm -e the new kernel? Then try to reinstall it via yum install. You > > should delete the new kernel from /var/cache/yum first. > > > > Just a point in why I say that is I have seen several machines that have > > yummed corrupt packages and bad repo metadata. After pegging yum to > > pull from a distinct mirror the problem has gone away. > > > > John > > How about this: I downloaded the new kernel rpm again manually then used > rpm2cpio to load the files into a work directory then ran this script: > > $ rpm -qlp ../kernel-2.6.18-194.3.1.el5.x86_64.rpm | while read rl > do > rstr=$(cmp $rl .$rl 2>&1) > rc=$? > if (( rc != 0 )); then > echo $rstr | grep -v "Is a directory" > /dev/null > rc=$? > if (( rc == 0 )); then > echo "Error: $rstr" > fi > fi > done > Error: cmp: ./boot/initrd-2.6.18-194.3.1.el5.img: No such file or directory > Error: cmp: ./lib/modules/2.6.18-194.3.1.el5/build: No such file or directory > Error: cmp: ./lib/modules/2.6.18-194.3.1.el5/source: No such file or directory --- And that would be correct because there are not there. There generated on the kernel install by the the rpm header that contains the mkinitrd script in kernel-rt or kernel.spec. John