[EMAIL PROTECTED] writes: > > > My only other "complaint" is that the only way I've found to alter > > variables in my driver is mdb -kw (not user friendly), or ndd. Ndd > > confuses the heck out of me, and I would dearly love to have some > > abstraction wrapped around it to make people with brains as small as > > mine be able to use it. It seems about 5x as hard as sysctl and 10x > > as hard as ethtool, for example. Maybe I just have a mental block. > > My recent proposal for dladm/wifi proposes a new "link properties" > mechanism for dladm(1M) that we hope will present a convenient and easy > way to administer link-specific properties. Right now, the properties are > specific to WiFi, but the current plan is to extend this to adjust other > per-link properties.
I just read this. The part that concerns me is in 2.3: "... Unlike legacy utilities such as ndd, the semantics and allowed values of each property will be known to dladm, reducing the incidence of administrative mistakes:" Does this mean that I don't have any way to use a custom property in my driver? (eg, dladm set-prop -p fluxcapacitor=on myri10ge0). Or does it mean that the driver needs to supply the semantics? Drew _______________________________________________ networking-discuss mailing list [email protected]
