On (03/05/08 15:31), Peter Memishian wrote:
>
> > Thinking about this somewhat further, I have my doubts about the utility
> > of a writable "default". As I see it, Brussels properties are now
> > persistent. Why would an administrator change a "default" independently
> > of changing the lasting persistent ("non-default") value? Its just not
> > clear in the context of Brussels what the point of maintaining a second
> > persistent value is.
>
> The idea would be to provide a general default value that would be more
> applicable for their configuration, but then still provide an ability to
> override it persistently on a per-link basis if needed. As we bring more
> properties into the mix, I could see some meaningful combinations -- e.g.,
> default Wake-on-LAN settings that one might want to configure across all
> applicable links. Existing properties such as the WiFi radio or powermode
> settings may already be things the administrator would like to set a
> different persistent default value for.
this would really match the driver.conf "default
global to all instances" model. I think that this
needs more thought so that we come up with an
extensible design.
I agree with Garrett that we could take the more
conservative approach here, and define "reset-linkprop"
to be the equivalent of
Use DLDIOCGETPROP with DLD_DEFAULT to get default_value;
Use DLDIOCSETPROP to set default_value obtained from previous step.
--Sowmini
