BothSun Update Manager andsmpatch analyze list a x86 security patch on a SPARC system (E450).
118669-05 J2SE 5.0_x86 update 6 patch, 64bit
The correct patches for SPARC might be 118666-04 J2SE 5.0: update 5 patch or 118667-04 J2SE 5.0: update 5 patch, 64bit.
Michael
I'm seeing the same thing. Another thread is suggesting that this may be a known issue (although it talks about sun4v).
I would argue that there should be a way to tell UM to ignore patches. Do I really need to see the GigaSwift patch every time I go into UM? I'm just running a Blade 100 at home, after all.
Just my 1.5 cents' worth.
Rainer
Hello Rainer,
I'm using a script that
fetches the list of available patches,
checks if these patches have "saved" (see below for explanation),
builds a list of the new (not saved) patches, downloads these patches and
finally request the installation sequence for the downloaded patches.
I am keeping the downloaded JAR-files, that's what I'm calling "saved".
When checking if a patch was already downloaded, it's quite easy to check if the patch is on your "own blacklist" of patches that shouldn't be installed.
I would recommend that you review Patch Check Advanced (PCA) by Martin Paul (http://www.par.univie.ac.at/solaris/pca/). This is very sophisticated tool, my script is a toy.
Michael
