Hi, I sent an earlier version of this proposal to the clearview-discuss list, and I'd like to get some comments from the SMF folks about how I plan to handle converting data stored in /etc/dladm/aggregation.conf and /etc/dladm/linkprop.conf during an upgrade (for example, S10 to Nevada) and handling attempts to set config data in an alternate root.
In both cases, I would like to make use of /var/svc/profile/upgrade. I've been told that I would need a contract in order to use that interface. Is that true? Am I only allowed to place SMF commands in that file or are dladm commands allowed? dladm commands would be simpler, and in at least one case (an alternate root environment that is an older OS version) I would need to use dladm commands. For upgrades: I would write a preinstall script for the package[s] that include aggregation.conf and linkprop.conf. The script would parse the files, generate the appropriate dladm commands, and append them to /var/svc/profile/upgrade. Question: When does /var/svc/profile/upgrade execute during boot? I would need linkmgmtd running before that script executes. We're going to put linkmgmtd in the seed repository. linkmgmtd doesn't depend on anything, and network/physical and system/device/local depend on it, in case that helps determine what runs first. For alternate roots: dladm would append dladm commands to [altroot]/var/svc/profile/upgrade. Again, I have the same question about when, during boot, this script executes. thanks, Dan
