Earlier quoted context omitted.
I disagree. It's possible to get advanced output from various command line tools in Linux, and it's possible to get networking information. It's much more difficult to do that on other OSs, especially Windows. I loathe debugging network troubles in Windows, because there is essentially no information. OS X has most of your standard tools, though some in some odd places, e.g., printing the routing table not being done…
airport -s is incredibly important in setting up roaming correctly with heterogeneous APs. You absolutely want SECURITY column to be identical, else devices won't roam. > There's no way I'll remember it I have history(1) and a symlink in a toolbox git repo. > you likely can't Google it "!g OSX airport command" works fine > route I found netstat -r is the most "Unix-portable" way of querying the routing table (Windows…
> "!g OSX airport command" works fine
Of course. The parent was referring to a situation when someone lacks internet access, due to a networking problem they are trying to fix, rendering them unable to use Google to find the command.