This is usually caused by not installing the optional updates. One of the reasons why (prior to SLES10), I always ran online_update from the command line, and not via YaST.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Wednesday, January 10, 2007 3:23 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: How do I find ... The tool that is supposed to tell you is Spident, but I don't find it to be reliable. Below are the output from two of my systems, both recently updated with every patch available from SuSE at the time it was updated... rockhopper:~ # SPident CONCLUSION: System is NOT up-to-date! found SLES-9-s390x-SP1 + "online updates" expected SLES-9-s390x-SP3 rockhopper:~ # exit mfl10:~ # SPident Summary # of packages (787) Product/ServicePack conflict match update (shipped) SLES-8-Int-s390 1 0.1% 451 57.3% 126 (896 50.3%) SLES-8-s390-SP2 0 0% 13 1.7% 42 (141 9.2%) SLES-8-s390-SP3 2 0.7% 76 9.7% 65 (286 26.6%) SLES-8-s390-SP4 0 0% 109 13.9% 83 (264 41.3%) Unknown 152 19.3% CONCLUSION: No supported Product/ServicePack found at all! mfl10:~ # Again, both systems were updated using the Online Update. At some point, I'd assume that you'd pick up everything that would have been found in the service pack, but obviously, the systems don't think so. So my question is: If you're using Online Update, is there a way to actually bring a system up through the Service Packs? And / or why doesn't Online Update supply all the fixes that the Service Packs do? What's the proper way to do this? -- .~. Robert P. Nix Mayo Foundation /V\ RO-OC-1-13 200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ ----- "In theory, theory and practice are the same, but in practice, theory and practice are different." ---------------------------------------------------------------------- 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
