Cathy Zhou wrote On 02/16/06 00:39,:
>An updated version of the Vanity Naming and Nemo Unification design >document is now available at: > > http://opensolaris.org/os/community/networking/uv-design.pdf > Cathy, Section 3.1.3 contains the statement: Link names can be any valid style-1 DLPI provider name, which is a composition of the driver name obeying the constraints identified in the NOTES section of dlpi(7P)and a PPA number. Since link names always have a style 1 device node, there are no PPA numbers and the PPA number name syntax is not relevant. The text here implies that there is a requirement of at least one trailing numeric character in a link name; this requirement, if present, should be removed and the text clarified. In principle, style 1 DLPI device names never had the numeric suffix requirement but we codified the practice in the belief that there could be applications that don't support (or have never been tested with) style 1 devices and names. Now, by defining a new name space and access method (libdlpi) the FUD is gone and we should do the more flexible thing. To put this in real terms, we should expect that in the future, people will want to name their links after their zones, services, domains, etc. and we should not create unnecessary restrictions here. (It's unfortunate that we can't avoid the 15-byte length restriction due to IFNAMSIZ, and Solaris's international character situation is too messed up to allow non-ASCII characters.) -=] Mike [=- _______________________________________________ networking-discuss mailing list [email protected]
