> Parseable Output Format > > Many dladm subcommands have an option which displays output in a > machine-parseable format. The format is 0 or more lines with the > following syntax: > > <key>="<value>" [<key>="<value>" ...] > > Note that <value> is always surrounded explicitly by > double-quotes to make parsing of values with embedded space > characters easier. Also note that <value> may be the empty > string if the key is not associated with a value.
The above looks good, though it'd be nice for us to cover some additional guarantees, like the possible characters that might appear in "key" (e.g., key will never contain an '='. But all of that should wait until the reworked parseable format. > > Another aside: IIRC, we had this display the STATE, SPEED, and DUPLEX so > > that we could depecate show-dev. But STATE is already covered by > > show-link, DUPLEX will be covered by show-ether, and MEDIA and SPEED > > probably belong in show-link. So in other words, I think we could > > simplify things a bit post-UV. > > Would you like to throw this cleanup in with 6651255? There are no > manpage AIs from this aside, correct? No manpage AIs at this time. I've no issue with generalizing 6651255 to cover all of this, though the removal of show-dev will require an announcement in an S10 update release. We'll also need coordinate all of this with Raoul from the doc side, of course. > > > Deletes the specified aggregation. > > > > > dladm add-aggr [-t] [-R root-dir] -l linkn ... link > > > > The above should probably be "link ... linkn" > > No, the last argument is the name of the aggregation. The arguments to > -l are the underlying links being added to the aggregation. Ah, I see the notation now. I got confused by "linkn" since I was thinking "n" was supposed to be in italics. > It should probably be something like: > > -l link1 [-l link2 ...] link > > Is that better? Yes. > > > The MAC address of the link or port. > > > > > > PORTSTATE > > > > > > XXX > > > > Will be filled in soon? > > What is it PORTSTATE? Yes, it seems like PORTSTATE needs to be described. > FLAGS > > A set of flags associated with the VLAN link. > Possible flags are: > > f The VLAN was created using the -f option to > create-vlan. > > i The VLAN was implicitly created by plumbing an IP > interface on a PPA-hack DLPI device. These VLAN > links are automatically deleted on last close of > the DLPI device (i.e., when the IP interface > associated with the VLAN link is unplumbed.) The implicit case is not specific to IP interfaces (e.g., snoop will also cause them to be created). Also, I'm a little nervous about the term "DLPI device" (as opposed to DLPI link), and I'm not sure if there's precedent for saying "hack" in manpages ;-) -- meem
