3 ms·
> "ip" is useless as a keyword if you're looking for help online. I don't know the decisions behind the naming either, but the ip shell command comes as part
by erikb 8y ago
> "ip" is useless as a keyword if you're looking for help online.
I don't know the decisions behind the naming either, but the ip shell command comes as part of the iproute2 [1] package.
After I found out about this googling became much easier.
[1] https://en.wikipedia.org/wiki/Iproute2 https://en.wikipedia.org/wiki/Iproute2
- da_chicken 8y agoWell, sure, but assume you're new and you don't know that. You can usually search for "man ip" to get close, but that usually just gets you a technical reference for an experienced user (the man page) and not a tutorial, introduction, or training doc for someone learning a new tool. "ip command tutorial" works well, though the results are still rather mixed. I get Cisco and Windows results as well until I search "ip command tutorial linux". The point is that searching for "ifconfig tutorial" is going to give you what you want, while "ip route" is probably going to get you Cisco documentation, honestly. Even something like "parse ip output" is going to give you a mix of results from Linux, Windows, or web services while "parse ifconfig output" is a lot more clear. "ip" is simply a saturated keyword, making it a bad keyword.
- erikb 8y agoNot sure why you think I would disagree. I'd say that is exactly my opinion, so I wanted to share that googlable term with the other frustated people out there.
- da_chicken 8y agoI don't think you'd disagree. I just think, "Well, you could search for iproute2," isn't that helpful because it's not that obvious that that is the package name.