> - I don't have a particularly strong feeling on the naming of set-prop > and friends, but I don't personally feel the longer set-linkprop > alternative suggested particularly improves the syntax. One argument > that I didn't see expressed was that, in general, the object of most of > the commands is the link name, so to me the absence of "link" from these > command names is unlikely to be particularly confusing.
Yes, I had intended to convey this as well but probably failed. > - In the scan-wifi and show-wifi output, why not use SECURE (SECURITY > would be even better) instead of just SEC? I think the proposed SEC > abbreviation is a little too short. The issue is simply one of space -- "SECURE" pushes us over the 80-column "limit", which means another field has to go or be compressed. We could compress the LINK field, but we should do so across all dladm subcommands; ESSID is another candidate for compression, but I worry that may cause formatting mayhem in common use-cases. Maybe my concern is unfounded, though? Further, given that we use the abbreviation elsewhere (e.g., set-secprop) -- not to mention things like IPsec -- it didn't seem an unreasonable abbreviation to me. -- meem
