> Why not go all the way? Why keep a separate ipv4-routing value if it > can conflict with the general/enabled properties of the services > themselves? Why not report ipv4-routing as true if and only if any of > the services are enabled, and if the user asks to enable it, enable the > chosen service?
i think that would work. >> the problem there is that routeadm settings may be changed >> during boot on the basis of probing network configuration that >> may have changed since last boot, so i think we're stuck with it. > > Please elaborate. see: http://cvs.opensolaris.org/source/xref/on/usr/src/cmd/svc/milestone/net-init from line 172 on. we set revert values for routing options (specified via the -b option) on the basis of whether any default routes have been specified. if none have, we specify the default to revert to as ipv4-routing enabled). now we could probably get rid of the "-u" on every boot here (though it would be needed for the first reboot post-upgrade to migrate configuration to smf daemon services - we could use a first_boot option that we set to false after the first upgrade boot). alan This message posted from opensolaris.org
