> > I noticed that we still support "dladm -R option" by writting the dladm > > commands into the <altroot>/var/svc/profile/upgrade script. But I am > > wondering whether they should be written to the > > <altroot>/var/svc/profile/upgrade_datalink script instead (which is the > > same > > script used for the system upgrade). If we do so, if someone runs "dladm > > create-aggr -R" command and also touched a <altroot>/etc/hostname.<link> > > for > > this aggregation, the aggregation can be created early enough. > > > > The downside of this approach is that the alternative system must be > > post-vanity-naming, which knows to run the > > /var/svc/profile/upgrade_datalink > > script in the net-physical service. > > What do you think?
Given that /var/svc/profile/upgrade won't work right for aggregations, I think we have to write to /var/svc/profile/upgrade_datalink going forward. However, if we must support -R to alternate roots that are older than the booted environment (is this required?), then we might have to do something cheesy like looking for the existence of /sbin/dlmgmtd and writing to /var/svc/profile/upgrade if it doesn't exist. -- meem
