Sebastien Roy wrote:
> Peter Memishian wrote:
>> The mention of "aggr" here seems a bit strange since we no longer use it
>> elsewhere in the manpage. It might make sense to keep it given that it
>> would simplify some of the descriptions of the aggr subcommands, but OTOH
>> if we did that, we'd probably want to follow-suit with "vlan" and (one
>> day) iptun. (However, if we do decide to keep it, it should be changed to
>> say "aggregations of datalinks".)
>
> I agree, and it does simplify the subcommand descriptions. I'll send out
> an update once I've made all of the associated changes.
While making these changes, it occured to me that using something
specific for WiFi links, physical links, and Ethernet links would all be
consistent with the spirit of your comment. Something like:
Each dladm subcommand operates on one of the following
objects:
link A datalink, identified by a name.
plink The link name of a physical datalink.
elink The link name of an Ethernet datalink.
vlan The link name of a VLAN datalink.
wlan The link name of a WiFi datalink.
dev A network device, identified by concatenation of a
driver name and an instance number.
aggr An aggregations of datalinks, identified either
by a link name or an administratively-chosen key
between 1 and 999.
secobj Secure objects, identified by an
administratively-chosen alphanumeric name.
This allows the synopsis of all subcommands to be very clear about what
kinds of links they operate on, and not generic links of any class or type.
-Seb
