> The final set of updates based on comments from Meem and Jim: > > http://www.opensolaris.org/os/project/clearview/dladm-uv-brussels.1m.txt
| 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. The definition for "secobj" above needs to follow parallel structure -- e.g., "A secure object, ". | Some subcommands require a specific type of link. For | instance, the WiFi subcommands require a WiFi link. Is this bit still needed given the new naming conventions? | Create a tagged VLAN link with an ID of "vid" over Ethernet | link "ether-link". The name of the VLAN link may be | specified as "vlan-link". | | If the name is not specified, a name will be automatically | generated (assuming that "ether-link" is <name><PPA>) as The above two paragraphs could be merged. | For example, if "ether-link" is bge1 and the VLAN ID is 2, | the name generated will be "bge2001". For consistency, s/VLAN ID/"vid"/ | VID | The VLAN ID associated with the VLAN. s/VLAN ID/ID/ (to eliminate redundancy). | General Link Property | | The following general link property is supported: Still needs to be made plural :-) -- meem
