On Saturday 03 April 2004 18:43, Jeff Johnson wrote: > What's needed is context, not details. There's a chance that something > other than up2date is/was at fault. OK, I am not sure what you mean by "context". I started noticing problems with up2date not handling a situation when a package install/update was not completed (as far as I can determine because of selinux policy failures) -- https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119538 I then attempted to update to the latest version of policy (1.9.2-9) and hit a problem where up2date/rpm was not removing an rpmdb entry for a package that was installed (but perhaps not correctly ... see below) -- https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119946 I made sure that I had the same general levels of updates on a second system (especially that rpm was the same). Everything looks good. OK, lets reboot ... oops kernel panic rebooting -- https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119981 ... cannot load/find policy reboot with enforcing=0 ... read the rest in the bugzilla report. So, "context" ... please be a bit more specific in what information you are looking for. I will be happy to gather anything I can but I cannot tell what that is from your "context" comment. Gene
