Sean, With the AI installer, we could potentially use an older svccfg to apply a profile to a newer repository and vice versa.
From this mail, it sounds like the former case would fail? thanks, -ethan Sean Wilcox wrote: > Flag Day : These fixes will integrate in the next few days once the > final RTI is approved. > > With the integration of the following bug fixes : > > 6411391 Empty method_context's don't work > 5093847 importing a manifest should create method_context properties > even if not set > 6517270 partial method context definitions should work > > <method_context> entries will become more friendly and allow for correct > inheritance of values due to changes in the DTD. > These changes require that the SMF repository db be restructured in a > way that old restarter and svccfg implementations will not understand. > Tools or procedures that mix the old smf with the new repository > database will cause problems, by potentially intermixing the repository > and smf utilities. > > --- > Backwards BFU across build snv_109 will require a reseed of the > repository with the old svccfg to reload the repository in a readable > format by the old restarter. > > The following step should be executed after the BFU has completed, and > before a reboot. > > This step will reboot the system so make sure all conflict resolution is > complete : > /lib/svc/bin/restore_repository > > Note : any modifications to the repository will be lost with this process. > > In order to save any modifications, the following step can be applied to > those modified services. > svccfg export <service name> > <filename> > > Once the bfu and reseed/reboot have completed, use svccfg import to > apply the exported manifest files. > Forward BFU has been modified to use the correct DTD with the correct > svccfg. > >
