Meem,
Line spacing and paragraph breaks will be different--and I hope better--
in the man page as a customer would view it ("man dladm" or on
docs.sun.com). What we're looking at in this email is man command
output piped through "col -x -b", which produces extra line spaces.
As to:
> tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRI-
> BUTE TYPEATTRIBUTE VALUE _ AvailabilitySUNWcsu _ Interface
> StabilityEvolving
[ ... ]
> tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRI-
> BUTE TYPEATTRIBUTE VALUE _ AvailabilitySUNWcsr _ Interface
> StabilityEvolving
?
This will end up looking like our standard Availability/Interface Stability
table.
Terry
> Subject: re: [clearview-discuss] review for merged UV/Brussels dladm(1M) man
page
> To: Sebastien Roy <Sebastien.Roy at sun.com>
> Cc: clearview-discuss <clearview-discuss at opensolaris.org>,
Terry.Gibson at sun.com, brussels-dev at opensolaris.org
> MIME-version: 1.0
> Content-transfer-encoding: 7BIT
> X-PMX-Version: 5.2.0.264296
> X-Authentication-warning: dhcp-cbjs05-219-62.PRC.Sun.COM: meem set sender to
peter.memishian at sun.com using -f
>
>
> > Some devices do not support configurable datalinks or
> > aggregations. The fixed datalinks provided by such devices
> > can be viewed using dladm, but can not be configured.
>
> After UV, which devices would these be?
>
> > For example, suppose that the bge0 device has a link name of
> > mgmt0 (because the administrator initially named it such by
> > typing "dladm rename-link bge0 mgmt0".) The bge0 device is
> > physically removed from the system due to failure, and replaced
> > with a ce0 device. To associate the newly added ce0 device
> > with the mgmt0 configuration previously associated with bge0,
> > the administrator types "dladm rename-link ce0 mgmt0"
>
> The above paragraph belongs in EXAMPLES.
>
> > dladm show-dev [-p] [-s [-i interval]] [-o field[,...]] [dev]
>
> Should we state that this is deprecated?
>
> > Show device configuration information (the default) or
> > statistics, either for all network devices or for the
> > specified device dev.
>
> An aside: most of the stuff shown by show-dev seems redundant given
> show-link and show-ether. We should probably file an RFE to have it
> gutted, and have show-link display the speed.
>
> > -p, --parseable
> >
> > Display using a stable machine-parseable format.
>
> Doesn't seem like we document what that format is anywhere in the manpage.
>
> > dladm show-phys [-pP] [-o field[,...]] [link]
> >
> > Show the physical device and attributes of all physical
> > links, or of the named physical link. Without -P, only
> > physical links which are available on the running system are
> > displayed.
>
> 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.
>
> >
> > dladm create-aggr [-t] [-R root-dir] [-P policy] [-L mode]
> > [-T time] [-u address] -l linkn ... link
>
> Need a paragraph break here.
>
> > Combine a set of links into a single IEEE 802.3ad link
> > aggregation named "link". The use of an integer "key" to
> > generate a link name for the aggregation is also supported for
> > backward compatibility. Many of the aggr subcommands below
> > also support the use of a "key" to refer to a given
> > aggregation, but use of the aggregation link name is preferred.
> > See the NOTES section for more information on keys.
>
> > dladm modify-aggr [-t] [-R root-dir] [-P policy] [-L mode]
> > [-T time] [-u address] link
>
> Need a paragraph break here.
>
> > Modify the parameters of the specified aggregation.
>
> > dladm delete-aggr [-t] [-R root-dir] link
>
> Need a paragraph break here.
>
> > Deletes the specified aggregation.
>
> > dladm add-aggr [-t] [-R root-dir] -l linkn ... link
>
> The above should probably be "link ... linkn"
>
> > -l, --link
> >
> > Specifies a link to add to the aggregation. Multiple links
> > can be added by supplying multiple -l options.
>
> This doesn't seem to match the notation above.
>
> > dladm remove-aggr [-t] [-R root-dir] -l linkn ... link
>
> Likewise.
>
> > Removes links from the specified aggregation.
> >
> > -l, --link
> >
> > Specifies a link to remove from the aggregation. Multiple
> > links can be removed by supplying multiple -l options.
>
> Likewise.
>
> > The MAC address of the link or port.
> >
> > PORTSTATE
> >
> > XXX
>
> Will be filled in soon?
>
>
> > VID
> >
> > The VLAN tag or ID associated with the VLAN.
>
> Might be clearer as "The VLAN tag (ID) associated with the VLAN."
>
> > FLAGS
> >
> > A set of flags associated with the VLAN link. The
> > only flag possible is 'f', which denotes that the
> > VLAN was created using the -f option to create-vlan.
> > More flags may be defined in the future.
>
> Need to add 'i' (for implicitly created VLANs).
>
> > General Link Property
> > The following general link property is supported:
> >
>
> As Cathy mentioned, "autopush" needs to be covered.
>
>
> > Ethernet Link Properties
> > The following MII Properties as documented in ieee802.3(5)
> > are supported in read-only mode:
> >
> > o link_duplex
> >
> > o link_up
> >
> > o adv_autoneg_cap
> >
> > o adv_1000fdx_cap
> >
> > o adv_1000hdx_cap
> >
> > o adv_100fdx_cap
> >
> > o adv_100hdx_cap
> >
> > o adv_10fdx_cap
> >
> > o adv_10hdx_cap
>
> Would be really nice to find a way to remove the blank lines in the above
> list. (This manpage is long enough already ;-)
>
> > EXAMPLES
>
> Would be nice to see some UV examples here :-)
>
> > tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRI-
> > BUTE TYPEATTRIBUTE VALUE _ AvailabilitySUNWcsu _ Interface
> > StabilityEvolving
> [ ... ]
> > tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRI-
> > BUTE TYPEATTRIBUTE VALUE _ AvailabilitySUNWcsr _ Interface
> > StabilityEvolving
>
> ?
>
> --
> meem
