The fastest way to update everything that is already installed on your system (note that this is not necessarily the _best_ method) would be to make the contents of the CD available to your system (NFS, SMB), "cd" to the directory where the RPMs live and do "rpm --test -Fvh *.rpm" and then go away for a while. If that comes back OK, then do it again without the "--test" switch.
I suspect the more official method would be to use YaST: yast -> Software -> System Update This can be done via the GUI, but I would recommend SSH and avoid the GUI. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of John Kapturowski Sent: Friday, April 16, 2004 10:27 AM To: [EMAIL PROTECTED] Subject: Maintenance procedures (SLES8, CD2) Hi all, we are just starting out and am learning the hard way. But I will need/want to put on maintenance (CD2) to our Suse, SLES8'ed, 31-bit, LPAR system. I went to the archives but keep on getting sidetracked and a bit confused. It seems like there are countless ways that everybody has experienced over the years. We have a brand new system, no RPM's on, except what may have been included on the initial release. So, what do I do? Init the RPM, etc...Thanks John Kapturowski Erie #1 Board of Cooperative Education Services West Seneca, NY PS, all the snow is gone, I think.... ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
