Maybe in new tools they should randomly change the formatting every run so that people can't parse the output.
There are real reasons for Linux to replace ifconfig, netstat, etc
31–40 of 270 posts
Re: There are real reasons for Linux to replace ifconfig, netstat, etc
#32I'm trying hard to fight my old muscle memory to use ip instead of ifconfig on Linux. I have a few issues though: * "ip" is useless as a keyword if you're looking for help online. It's extremely frustrating and probably my main issue actually learning how to use the damn thing. * ifconfig's output is simply more readable IMO: https://svkt.org/~simias/up/20180525-113825_ip-vs-ifconfig.p... . It's pretty weird that a b…
> ifconfig's output is simply more readable IMO Yes, this is key, and why ip is so terrible for the way I currently work. No doubt I'll have to get used to it, like those stupid biosdevname interfaces. 90% of my machines don't have more than 1 IP per physical interface, the rest are aliases ifconfig outputs clear whitespace, so picking out the specific details of - interface name - ip address Is far easier. I do pref…
to get the gateway: ip route show default
> > ifconfig's output is simply more readable IMO
I prefer iproute2's terseness.
Re: There are real reasons for Linux to replace ifconfig, netstat, etc
#33Why did they have to make the output of `ss` so cumbersome? I often end up installing the legacy tooling just so I can have `netstat`
It seems like a missed opportunity not to have a JSON (or other explicitly machine readable format) output option for easy scripting use through jq. Every time I need to craft a grep regex to get some trivial piece of information from one of these tools, I feel there's a bug waiting to happen (and I'm usually right).
I'd appreciate it... would also make generating pretty UIs around console applications easier as well.
Re: There are real reasons for Linux to replace ifconfig, netstat, etc
#34Why did they have to make the output of `ss` so cumbersome? I often end up installing the legacy tooling just so I can have `netstat`
It seems like a missed opportunity not to have a JSON (or other explicitly machine readable format) output option for easy scripting use through jq. Every time I need to craft a grep regex to get some trivial piece of information from one of these tools, I feel there's a bug waiting to happen (and I'm usually right).
Powershell is on linux now... ;)
Re: There are real reasons for Linux to replace ifconfig, netstat, etc
#35I'm trying hard to fight my old muscle memory to use ip instead of ifconfig on Linux. I have a few issues though: * "ip" is useless as a keyword if you're looking for help online. It's extremely frustrating and probably my main issue actually learning how to use the damn thing. * ifconfig's output is simply more readable IMO: https://svkt.org/~simias/up/20180525-113825_ip-vs-ifconfig.p... . It's pretty weird that a b…
> "ip" is useless as a keyword Most docs will mention iproute2. You can use that for googling.
Yeah that’s what I loved about this article, I finally know what to google.
Re: There are real reasons for Linux to replace ifconfig, netstat, etc
#36I'm trying hard to fight my old muscle memory to use ip instead of ifconfig on Linux. I have a few issues though: * "ip" is useless as a keyword if you're looking for help online. It's extremely frustrating and probably my main issue actually learning how to use the damn thing. * ifconfig's output is simply more readable IMO: https://svkt.org/~simias/up/20180525-113825_ip-vs-ifconfig.p... . It's pretty weird that a b…
The man page is good. `ip` takes a --oneline arg to make it more parseable.
I'm not sure having everything crammed into a single line makes it better (at least if a human is supposed to parse it and not a machine): https://svkt.org/~simias/up/20180525-125636_ip-vs-ifconfig-2...
Re: There are real reasons for Linux to replace ifconfig, netstat, etc
#37"... an ongoing effort to obsolete the old, cross-Unix standard network administration and diagnosis commands of ifconfig, netstat and the like and replace them with fresh new Linux specific things like ss and the ip suite."
Old does not mean bad but Linux chooses that path as it moves further away from UNIX and being a Unix-like system in its pursuit to be Windows.
Re: There are real reasons for Linux to replace ifconfig, netstat, etc
#38Why did they have to make the output of `ss` so cumbersome? I often end up installing the legacy tooling just so I can have `netstat`
It seems like a missed opportunity not to have a JSON (or other explicitly machine readable format) output option for easy scripting use through jq. Every time I need to craft a grep regex to get some trivial piece of information from one of these tools, I feel there's a bug waiting to happen (and I'm usually right).
ip has a --json flag: https://github.com/CumulusNetworks/iproute2/commit/5df607725...
Re: There are real reasons for Linux to replace ifconfig, netstat, etc
#39Earlier quoted context omitted.
It seems like a missed opportunity not to have a JSON (or other explicitly machine readable format) output option for easy scripting use through jq. Every time I need to craft a grep regex to get some trivial piece of information from one of these tools, I feel there's a bug waiting to happen (and I'm usually right).
Powershell is on linux now... ;)
The most underrated tool barely used outside of Windows sysadmin world.
Re: There are real reasons for Linux to replace ifconfig, netstat, etc
#40I'm trying hard to fight my old muscle memory to use ip instead of ifconfig on Linux. I have a few issues though: * "ip" is useless as a keyword if you're looking for help online. It's extremely frustrating and probably my main issue actually learning how to use the damn thing. * ifconfig's output is simply more readable IMO: https://svkt.org/~simias/up/20180525-113825_ip-vs-ifconfig.p... . It's pretty weird that a b…
> "ip" is useless as a keyword Most docs will mention iproute2. You can use that for googling.
That's a good tip, thanks.
That being said while docs specifically written about the tool will probably mention it random forum posts, tutorials or even stackoverflow questions may not.