Hi, Here's what I'd like to do for the alternate root and upgrade cases.
I'd like to get some opinions here before I head over to SMF discuss or other lists. upgrade: For example, going from S10U4 to Nevada. - write a preinstall script for the package or packages that include aggregation.conf and linkprop.conf. - The script would parse the existing aggregation.conf and linkprop.conf, then write commands to /var/svc/profile/upgrade to load the information from those files into the linkmgmtd SMF repository. - The commands could either be dladm or SMF commands. I understand the preference is for SMF commands. dladm commands would be easier. SMF commands are harder because what do I use for a link ID? I could use an invalid link ID and then have linkmgmtd recognize that a link ID needs to be allocated for such entries. alternate root: - dladm would write out dladm commands to the /var/svc/profile/upgrade script off of the alternate root. SMF commands would be fairly easy here because we could use linkmgmtd to come up with unique linkids. One problem is what if the alternate root is for an environment that predates linkmgmtd? Is such a thing possible? Note that we would need a contract with the SMF folks for using /var/svc/profile/upgrade. thoughts? Things I missed? thanks, Dan
