On Thu, 2004-09-02 at 03:01, shrek-m(a)gmx.de wrote: Very likely, yes. The rpm for yum was part of that update (it was for me) and it looks like the same error I got. Considering how much Seth said the code base changed (and particularly that making a newly installed kernel the default isn't implemented yet), it's no surprise that since yum was updated while it was running, that it bombed out when it tried to update the bootloader. Just edit /etc/grub.conf manually and change the 'default=' line to the appropriate value, or just select the right kernel during boot boot and then remove the old kernel(s). But be prepared for some possible brokenness that some of us have been experiencing ;-). -- -Paul Iadonisi Senior System Administrator Red Hat Certified Engineer / Local Linux Lobbyist Ever see a penguin fly? -- Try Linux. GPL all the way: Sell services, don't lease secrets