Hi, I've been running into problems with Linux totally locking up during extremely large updates. This leaves the state of the update indeterminate and the state of RPM's database a complete mess. Obviously, there are lower-level issues that need to be fixed elsewhere. However, what would be truly valuable would be the addition of either: a) --recover (which would analyze the yum cache and RPM database to determine where yum had got to, then resume from that point) or b) --checkpoint and --restore (where --checkpoint tracks enough details of the progress that --restore can continue from where it left off) If there's a way to do this already, then I'd truly appreciate knowing how, as it's getting to be a real pain. The other thing that's proving irritating is dependency breakages, where one package is updated in an RPM database but not things that depend on it. It's possible to exclude things until the dependencies work again, but it would be cool if there was an option such that Yum could detect the failure than calculate every possible package that can't be updated (not just those that are directly affected, but anything indirectly impacted as well) and automagically exclude them, so that the installable updates can be updated without further ado. Any way of doing either of these things at present, or any plans to add these capabilities? Jonathan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
