> I agree, we should be able to use the description as a means of looking up t$
> 1- Duplicate descriptions are not allowed (should return EEXIST if an attemp$ Agreed. At least, unless and until someone comes up with reasonable semantics for handling multiple interfaces at once in all relevant calls. > 2- In order to prevent unpredictable behavior in the presence of name-"wm0" $ I think I would prefer that attempting to set a description that equals an interface name is rejected, and, when attaching an interface after boot (ie, after interface descriptions can have been set), when choosing an interface disambiguator number, putative names are tested for conflicts against not only other interfaces' names but against their descriptions as well. Together, these would mean that there is no overlap between the set of interface names and the set of interface descriptions. Of course, this means special handling for a zero-length description, or else that a zero-length description is different from no description, but I think that is the lower price. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML mo...@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
