> From: Aria Bamdad [mailto:[EMAIL PROTECTED] > > 1-After all packages are updated to SP1, if I issue SPident, > get a System is NOT up-to-date. It seems like it finds > SLES10 + updates and expects SLES10 SP1 even though I am at > the SP1 kernel level and the system login prompt says I am at > SP1 and so does /etc/SuSE-release. > Anyone else sees this problem or is it just me!
It is not just you! We get the same result. In our case it's a direct result of having installed Velocity's snmpd RPM for SLES10. I'm a little unhappy about the way this particular situation played out, as we apparently need Velocity's version of net-snmp for the updated MIBs, but SuSE have made it ever so slightly difficult to remove their version of it from SLES10 as it is required by hplip (the HP LaserJet drivers). In the end I just did a force install of Velocity's RPM over SuSE's. Perhaps there may have been a less rude method. The other package which causes us to not show a supported service pack in SPident is yast2-bootfloppy. This package exists in GA and is installed by default, and SPident expects to see an updated revision... but the actual package does not appear on my SP1 media. I don't know why. I think I'm going to solve the problem, now that I've identified it, by adding it to my list of packages to remove completely. I'm not sure what to do about the Velocity net-snmp issue. It would be nice, since I know nothing whatsoever about the issues, to have received an add-on (or "adjunct") package from Velocity, containing new MIBs to simply add to SuSE's net-snmp package. SPident -vvv should show you which packages are preventing it from achieving nirvana in your particular environment. ok r. ---------------------------------------------------------------------- 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
