On Thu, 2009-09-03 at 15:58 -0700, Danek Duvall wrote: > Rishi Srivatsavai wrote: > > > (1) Modify the existing datalink-management SMF service method to > > do the necessary checks on re-configure boot and add the necessary > > dladm commands to a upgrade script[2] that runs during network-physical. > > I think this is typically what we would suggest you do.
The downside of this approach is that something needs to check "is this a reconfigure boot?" at every boot, and that check will have to be done "forever". It also adds unnecessary overhead to reconfigure boots that occur after the upgrade has already been done (either subsequent upgrades, or reconfigure boots having nothing to do with upgrades). > > (2) Create a new SMF service that runs late in boot and also only once > > on boot after upgrade to perform the PVID update. Please share any pointers > > to existing SMF services that are similar and run just once. > > This might work, but I don't know much about services disabling themselves. > I would presume it's safe to run "svcadm disable $SMF_FMRI" from within the > script, but folks on greenline-discuss would know better. It looks like the svc:/network/inetd-upgrade:default does this. > > The question I see with this is whether this will ever need to be run > again. You have to keep delivering the service as long as you care about > transitioning people across this flag day (just like you would have to > carry the code in your postinstall script or upgrade script for that long), > but if you never have to run it again, then it can stay disabled and not > worried about until it's time for the service to be removed. It won't ever need to be run again. > My only other comment (and this is more in your domain that ours) is that > it sounds like this needs to be done earlier in boot -- won't network > connections already be established by the time this service runs, and won't > that make changing this configuration problematic? It adds a property to existing VLAN links, and this property won't be needed unless and until an administrator creates a bridge instance using dladm create-bridge (introduced by this project). It doesn't need to be done early in boot since the administrator won't have the opportunity to create a bridge until the login service has started. -Seb _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
