Angela Byrne - Solaris Sustaining wrote: > > Angela Byrne - Solaris Sustaining wrote On 10/17/06 14:54,: > >>So I assume this script was put in place for a reason.. >>As such, we need to follow this idea to genesis add SUNWicda to the miniroot >>- if that is possible... > > > So Peter Harvey challenged this saying that the package SUNWicda > would already be present but that the content would not contain the > required SBD changes.
But the one in U3 is a different VERSION in U2 we have VERSION=11.10,REV=2005.11.12.14.23 in U3 we have VERSION=11.10,REV=2006.08.16.17.07 So we need to pkgrm the old one and pkgadd the new one. Looks like FCS is differnet from U2 which is different from U3 VERSION, suspect u1 is also a different version. I think we will need to do this manually. That is a doc that explains 1 now to remove the old SUNWicda 2 install the new SUNWicda from U3 Doing all this at this late stage in a KU prePatchis too dangerous. A seperate patch coudl be created, but the KU would not depend on that patch ( unless it delivered non miniroot patch packages as well, and packages that are in the minimal metacluster as well ) That is still a lot of work/testing at this late stage So perhaps a info doc/sun alert to detail how to do this manually. Enda > > As such, could we just add a regular sparse patch pkg for SUNWicda into the > KU to contain the update 3 changes. > > For normal patch installation, SUNWicda is not present so this would not > affect the patch install. > > But when we patchadd -C, the package SUNWicda would be present and would > automatically get the required update. > > Is this reasonable or is there some other strangeness in the miniroot > to stop this. > > Angela >
