Casper.Dik at Sun.COM wrote: >> So, I have followed most of this patching in the minrroot thread. I have >> some comments to add: >> >> The miniroot is 'special' and owned by install. I agree that perhaps it >> shouldn't be special, but it is. >> > > As you suggested in your other mail "not making it special" would > be my preferred option. How can we make it "not special", perhaps > by making sure certain services are not required and can be removed? > (About 6 services have their script replaced with "exit 0"; if they > could be removed from the repository instead .....) > > >> If you read the man page for patchadd -C it says that you should only >> install patches that are recommended for the miniroot, such as >> install-related patches, like pkg commands, etc..this is a very limited >> set of patches. >> > > Unfortunately, patches with (boot) device support *must* be included > as do patches which fix issues in ACPI, pci and others. > 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. 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 > >
