[EMAIL PROTECTED] wrote: > >3. Observation: Also read that RPM itself may need to be updated first, >before running the other RPMs; however, > in the S/390 updates I see not RPM for RPM, so I'm assuming I'll be ok. > > You'll probably want to look at more than just the s390 updates. Unfortunately not all the current RH errata RPMs are available precompiled for s390 yet, and this doesn't necessarily mean they aren't applicable. Check out http://rhn.redhat.com/errata/rh72-errata.html to see what 7.2 errata updates are available as src.rpm's but not as s390.rpm's. If you have an older version installed already, download the latest srpm and see if you can --rebuild it for s390. You'll want to do this before you bring your system down to single-user mode because compiling these things can sometimes take a LONG time. Not everything will rebuild successfully (perhaps why they aren't available for s390 yet). But many will and then you'll have a nice shiny new s390.rpm ready to be installed. Btw, if you try to rebuild the Perl 5.6.1 src.rpm, please let me know if you were successful (mine failed on the study() test).
rpm -qi (product name without version) will summarize installed packages including it's version number near the top. rpm -qip (filename) is pretty much the same thing except it works with rpm files instead of an installed package As far as being live, I've found stuff to be pretty resilliant (to the point of removing openssh and server without affecting my currently open ssh sessions). Better safe than sorry though. ~ Daniel
