On 05/12/10 12:51 PM, Edward Pilatowicz wrote:
some quick questions.
how does this functionality interact with different network management
services, specifically network/physical:nwam and
network/physical:default? is network configuration only supported for
one of these methods? if so, what happens if that method is disabled
and another one is in use?
does enabling the svc:/network/dns/install have any interactions with
nsswitch.conf(4)? for example, is it an error to enable
svc:/network/dns/install if dns is not enabled via nsswitch.conf(4).
will the svc:/network/install service reconfigure interfaces that
already have an existing configuration?
will the svc:/network/install service ever unconfigure interfaces? for
example, if no install_ipv4_interface and install_ipv6_interface values
are specified, and the svc:/network/install service is brought online,
will it do anything?
I echo Ed's sentiments and generally have a concern about install-only
interfaces. (And services named as such.)
It'd be better to consider the direction that the interfaces are likely to
evolve in long-term and put the properties on the appropriate services.
It wouldn't have to change the implementation a great deal for now, but
leaves an interface that has a much better chance of evolving. It also
allows the opportunity for configuration switching of the style that
ipfilter uses now: either the properties or the files are authoritative,
and that's switchable and predictable rather than inferred.
liane
_______________________________________________
opensolaris-arc mailing list
[email protected]
