[brussels-dev] [clearview-discuss] review for merged UV/Brussels dladm(1M) man page

[Peter Memishian]

 > 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:

Yes, I think that would make things more precise.  One thing that's lost
in a strict list though is the relationships between the types of objects.
Maybe something like:

       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:
	  
		 plink     A physical datalink.
		 vlan      A VLAN datalink.
		 aggr	   An aggregation datalink (or a key; see NOTES)
		 elink     An Ethernet datalink.
		 wlan      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.

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

The latter is a bit more verbose but might help to keep it clear to the
reader which objects are links and which are something else.

-- 
meem