Sowmini.Varadhan at Sun.COM wrote:
>
>> Would the properties still end up in the show-linkprop output? If so,
>> even well-behaved admins are still subjected to a mountain of properties
>> that they shouldn't even be using, which seems bad. Or are you proposing
>> some way to hide these properties? (I'm nervous about that as well.) If
>> we're sure this stuff will be off the beaten path, maybe we could reduce
>> the number of properties to just `cap', `advcap', and `lpadvcap' (or
>> somesuch) with a commas-separated list of values?
>>
>
> I'd initially felt that we should just print the bare-basics (like speed,
> duplex, autoneg), but both Raymond and Garrett pointed out to me that
> reducing the properties will just cause admins to regress to ndd usage.
> We could, though, have a "show-linkprop" vs a "show-linkprop -v" - the
> former would print the bare-basics, e.g., just the r/w props, (using the
> same adv* names as ieee802.3(5)), and the latter could print all the
> local/peer props in their gory glory.
>
>
This seems to be better than we introduces a completely new dladm
subcommand. But a problem is what we should put in "-v" and what not.
Dividing by "r/w" could be a solution, but I am afraid it will not
satisfy all customer's need. Different users might care about different
properties, we might never know that enough. I agree that current
kstat/ndd output of everything might not be a good practice, but users
might already have their admin scripts based on this practice. If we
expose things in a one-stop dladm command(show-prop), customer will have
least pains to porting to this solution, IMHO.
> --Sowmini
>
> _______________________________________________
> driver-discuss mailing list
> driver-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/driver-discuss
>
