Peter Memishian wrote:
> > plink/vlan/aggr/elink/wlan seem a bit uneven. We should probably use
> > "link" for each, or ditch the link suffix. That is, either:
> >
> > phys/vlan/aggr/ether/wlan
> >
> > or
> > phys-link/vlan-link/aggr-link/ether-link/wlan-link
>
> With regard to Jim's email, s/wlan/wifi/
>
This is great stuff. All of this is making the man page much more
intuitive to read. For example, it becomes obvious that a VLAN can only
be created over an Ethernet link. :-)
Each dladm subcommand operates on one of the following
objects:
link A datalink, identified by a name. Some subcommands
operate only on certain types or classes of datalinks.
For those cases, the following object names are used:
phys-link A physical datalink.
vlan-link A VLAN datalink.
aggr-link An aggregation datalink (or a key; see NOTES)
ether-link An Ethernet datalink.
wifi-link A WiFi datalink.
dev A network device, identified by concatenation of a
driver name and an instance number.
secobj Secure objects, identified by an
administratively-chosen alphanumeric name.
I'll provide a pointer to the final manpage shortly with all of this
stuff incorporated.
-Seb
