On Tue, 31 Jul 2007 13:38:09 -0600 Mark Post said: >Only "SPident -v" (or -vv or -vvv) will tell you what it thinks is not = >updated. >
I tried that. It seems to think that the level of the packages need to be OLDER than they currently are. For some reason it is looking at levels for packages that are for SLES10+updates rather than SP1. Here is SPident -v: Summary (using 835 packages) Product/ServicePack conflict match update (shipped) SLE-10-s390x 0 0% 381 45.6% 91 (1992 19.1%) SLE-10-s390x-SP1 4 0.2% 737 88.3% 89 (2086 35.3%) Unknown 94 11.3% CONCLUSION: System is NOT up-to-date! found SLE-10-s390x + "online updates" expected SLE-10-s390x-SP1 >> 2-Is there any reason why we can't put the local installation source >> dirctory on a minidisk that is then moved between different linux >> guests on VM one at a time and mounted and used to apply the updates? > >No, other than it would be a lot of time spent fiddling with things when = >it isn't necessary. Just set up the guest with the installation files as = >an installation server, and add it to the other guests as an installation = >source. It's very easy, actually, and the network traffic wouldn't have = >to go out of the box (assuming you're using a Guest LAN or a VSWITCH). = >I'm not sure what your insistence on not having a network-based installatio= >n server is all about, but you seem to be going out of your way to make = >things harder for yourself. > Actually I am not trying to avoide a network-based installation. The SLES10 SP1 installation did not support a network based via FTP installation directly off the CDs. Now that I have the installation files on a filesystem, I have no problem setting up a server. ---------------------------------------------------------------------- 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
