TIL: iproute2 has a color, a brief/human mode, and a one-line mode. I think I am going to be aliasing ip -color to ip from now on. $ ip -br -c a # ip -brief -color address lo UNKNOWN 127.0.0.1/8 ::1/128 eth0 DOWN wlan0 UP 192.0.2.1/24 2001:db8::1/64 fe80::1/64 $ ip -br -c l # ip -brief -color link lo UNKNOWN 00:00:00:00:00:00 eth0 DOWN 00:12:34:56:78:9a wlan0 UP 12:34:56:78:9a:bc
The "-brief" switch is not mentioned in the default manpage, at least on my Ubuntu 16.04 installation. Why? This should be mentioned prominently, as it's so useful.
There are real reasons for Linux to replace ifconfig, netstat, etc
221–230 of 270 posts
Re: There are real reasons for Linux to replace ifconfig, netstat, etc
#222Earlier quoted context omitted.
Huh, does "ip" also support "tc" (traffic control) commands - qdisc is a queueing discipline... tc seems to be the an earlier thing from the people who brought us ip. tc must have the worst command line interface and documentation ever - it is very hard and very frustrating to use, like no other command line interface I've ever seen. I once tried to use tc and gave up after more than a day of trying, that is how bad…
MegaCLI (lsi hw raid control) sees your tc and raised you a few million awful flags.
Re: There are real reasons for Linux to replace ifconfig, netstat, etc
#223Earlier quoted context omitted.
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
#224When I started learning Linux when it was, I think, 0.99, I appreciated that so many commands where cross-Unix. It was a Unix lookalike. I could watch how something is done on one Unix, type this stuff into my Linux terminal, and get an equivalent result in Linux, and this helped a lot and created a sense of community. Now I see that Linux tears the standards apart, there are more and more obstacles with porting comp…
I think you're over-romantascizing the past here. Linux dropped the cost of using UNIX down to zero. And it's not like everything was this cross-UNIX Utopia where things worked from system to system consistently and reliably. We went from a set of highly proprietary and expensive OSes that ran on hardware that a common person had no access to to something that nearly anyone can use. That's way more important than hav…
BSD had already done that, better, and earlier. Let's not try to rewrite history.
Re: There are real reasons for Linux to replace ifconfig, netstat, etc
#225Earlier quoted context omitted.
I'm not sure what the point you are making here is. The developers behind "ifconfig" on Linux could support the new API (iproute2) just as the developers behind "ifconfig" on OpenBSD updated their software to support the new kernel API as they became available.
The point is that in the BSDs, ifconfig is developed and released together with the kernel. See, for example, https://svnweb.freebsd.org/base?view=revision&revision=31237... , where the author added support for hardware packet pacing. The commit touches ifconfig, socket header files, and various parts of the kernel all in one atomic change.
Re: There are real reasons for Linux to replace ifconfig, netstat, etc
#226Earlier quoted context omitted.
You may also want 'whereis' instead of 'which'. I use cope to colorize my output, which makes 'which' useless to me for most common commands, but 'whereis' still works. Edit for examples: $ which ip /usr/share/perl5/vendor_perl/auto/share/dist/Cope/ip $ whereis ip ip: /usr/bin/ip /usr/share/perl5/vendor_perl/auto/share/dist/Cope/ip /usr/share/man/man7/ip.7.gz /usr/share/man/man8/ip.8.gz
> whereis Thanks for this! After 14+ years of using Linux almost daily, I had never heard of this command. I learned something new today, so now it's time to go home!
Re: There are real reasons for Linux to replace ifconfig, netstat, etc
#227Earlier quoted context omitted.
A --json arg would be much more parseable. I wonder if they'd be against that?
They won't. In fact it is already implemented. Try `ip -json addr`. Not all subcommands support it though.
rascul@coyote:~$ ip -json addr
Option "-json" is unknown, try "ip -help".
rascul@coyote:~$ ip -V
ip utility, iproute2-ss160111Re: There are real reasons for Linux to replace ifconfig, netstat, etc
#228Earlier quoted context omitted.
Always wondered about this - is IP 'internet protocol' or something else, since it's much lower level than IP? I've been using IP route 15 for 15, maybe 20 years now and hinestly have no idea.
Yes, it is 'internet protocol' [0] and part of TCP/IP.[1] [0] https://en.wikipedia.org/wiki/Internet_Protocol [1] https://en.wikipedia.org/wiki/Internet_protocol_suite
Re: There are real reasons for Linux to replace ifconfig, netstat, etc
#229Earlier quoted context omitted.
Not to say I would be a great fan of Linux, but I think at this point it's quite clear it's the huge winner of OSes. Nearly all servers run on it nowadays, I think all relevant smartphones (not sure though, correct me if that's wrong), many desktop/laptop computers and even Windows is integrating more and more with Linux. With such a dominance there is not much point in syncing changes of the standard with other OSes…
Kernel won, userland didn't.
Re: There are real reasons for Linux to replace ifconfig, netstat, etc
#230Earlier quoted context omitted.
Yup, you could say that again. I cut my teeth in Linux while in high school for the most path. First year of college, I go to the engineering labs to get a job, it's all SunOS/Solaris. It's like driving a car! There were very few commands that were different! Now, Linux is slowly going rouge and changing everything in the supposedly name of "progress" I'm still salty as hell with the systemd rubbish. The problem is t…
A lot of these changes are reminding me, a 40+ year old recovering sysadmin, that I am being left behind by the technology world. I would imagine that there are a few others in the thread that read this article and felt similar.