>> >> Agreed. >> >>> Any suggestions for a way forward? >>> >> >> In the near term, this is hard, we have kind of a mess right now. >> There is no way I can see to make the patching process 'aware' of the >> miniroot. We have patches generated all over the company. And, as far >> as I know we have never done it this way in the past. >> >> I just read the additional info in this thread about how the miniroot >> is built(which I did not know before), and the use of the SUNWsibi >> package. Perhaps the near term answer is to ship this package in some >> way so that it can be applied to the miniroot after it is patched as >> you and James have suggested. This doesn't seem unreasonable to me. >> > Biut SUNWsibi has changed from FCS to u1 and again for U3, so what rev > of SUNWsibi do we ship in say KU 118855-29 for instance? I don't know.. I hadn't realized this. > > I shoudl be able to patch my U2 miniroot with a KU that will also > apply to my U3 miniroot ( at some point down the line ) > But SUNWsibi is different in u2 to u3 miniroot. ( at least build 5 of > u3 anyway ) Agreed. But, right now we cannot patch the miniroot with patches that overwrite critical miniroot files.
Please file an RFE to track this issue. I can add the appropriate Caiman keywords so that we track it as part of this work. I don't think this is a bug. It is the design of the existing miniroot that is causing this limitation. The software is working as designed, perhaps badly, but it is working as it has worked for a long time. The redesign of the miniroot to not be special will take some work. thanks, sarah *** > Enda >> The long term approach is to make the miniroot not special. We have >> this work as part of the work we are doing with Caiman. We recognize >> that this is an issue. >> >> My answers are likely unsatisfactory. Sorry... I don't have any magic >> answers for an immediate fix for this issue. >> >> thanks, >> sarah >> **** >> >> >>> Casper >>> >>> >> >> > >
