This is awesome Martin, my guess is it might make a patchdiag file more accurate then the real one since it would use the info that patchadd would use to decide if it needs to be installed.
I'll give it a test and see if the results match if I installed the CPU from the bundled install scripts, but I think this is a great solution. On Thu, Jun 16, 2011 at 8:26 AM, Martin Paul <[email protected]>wrote: > After the idea came up to create a special patchdiag.xref which only > includes the patches of a Critical Patch Cluster (CPU), I couldn't resist > and gave it a try. > > I downloaded the "CPU OS Cluster 2011/04 Solaris 10 SPARC" and hacked up a > script (mkxref, see attachment) which extracts the necessary information > from the patch READMEs, patchinfo and pkginfo files and creates a > patchdiag.xref file. The idea is that this can then be used with PCA to > patch systems to the state of the CPU without actually having to download > the +2GB file (on every system). > > Take care: The script is mostly untested. It's hard to verify whether the > patchdiag.xref it creates is 100% correct. It works with PCA, and I've > compared a few sample patches with their entries in the real xref file, and > they looked fine. The Recommended/Security flags are missing (they are not > in the patchinfo file), but this shouldn't matter. > > I'm including both the script and the patchdiag.xref file I created from > the above mentioned CPU. If anybody does some experiments with it, I'd be > happy to hear about it. Theoretically, one can generate xref files for any > set of patches with the script, which might be of use in other regards than > with the CPU as well. > > Martin. > > > > -- Jeff
