sowmini.varadhan at sun.com wrote:
> - All commands will take dladm-like flags for persistence, parseable
> output, column selection
I have no problem with persistence being the default. But I'm concerned
that having temporary as an option for everything might add significant
complexity without solving any real problem.
In general (thus this might apply to dladm as well) having an
administrator do experiments is a good thing. But having objects that
can have both a temporary and persistent existence, coupled with object
dependencies, makes things difficult both for the implementation (need
to check that a persistent object doesn't depend on a temporary object)
and for the user (need to understand what to do when an error is
generated by the implementation checking the above).
What problem does it solve? Not clear.
One can do experiments by just having separate enable/disable that are
decoupled from the create/destroy of the object, and that avoids the
complexity.
> - Property/tunable management:
>
> # ipadm {set,get}-module-prop -p <name>=<value> [<interface>]
>
> If no <interface> is specified, the property is set for all active
> interfaces.
You also need to answer what happens to interfaces that are created
after a property has been set. For instance, I might want to turn on
forwarding on all current and future interface.
Erik
