On Thu, Nov 08, 2007 at 08:59:54AM -0500, Peter Memishian wrote: > > > > I agree the / is cumbersome; I was never too happy with that compromise. > > > > Perhaps a dumb question (and perhaps already discussed in the > > deliberations about this; if so, just pretend this email doesn't > > exist), but why not 'BSSID_IBSSID=xxxx' ? > > There's no technical issue, but most felt that BSSID/IBSSID was more > understandable to humans when looking at the (normal) output for > show-wifi.
But -p is meant to be parseable by non-humans, no? *sigh* > In any case, this becomes a non-issue if we enhance things so that the > field names are omitted when -o is specified. That is, if a script did > something like "dladm show-wifi -p -o bssid", it should just get back the > values without any field names, since those field names are clear from the > script's request. This request is in the aforementioned bug (6515065). This: % eval $(dladm show-wifi -p) would be great (though only if dladm quotes things like ESSIDs correctly!). This: % dladm show-wifi -p -o essid,bssid | read essid bssid not so much, because the shell read built-in simply splits the line into two using $IFS, and ESSID could contain whitespace (which is typically in $IFS). Sure, one could then do this: % dladm show-wifi -p -o bssid,essid | read bssid essid but it's really not as good as "eval $(dladm show-wifi -p)". Nico -- _______________________________________________ networking-discuss mailing list [email protected]
