Live data from Hacker News

There are real reasons for Linux to replace ifconfig, netstat, etc

utcc.utoronto.ca

251–260 of 270 posts

Re: There are real reasons for Linux to replace ifconfig, netstat, etc

#251
post #243
post #222

Earlier quoted context omitted.

After working with it almost daily for years I'm finally fluent in MegaCLI. I can even understand the --help for the most part. Time to get a new job I guess.

Nah.. Just time to relearn it all with StorCLI instead.

:-(

Re: There are real reasons for Linux to replace ifconfig, netstat, etc

#252
post #102

Earlier quoted context omitted.

> What are people using them for? In my case, keepalived VRRP floating addresses.

I've used eth0:xx style aliases for that for a decade with no problem. Do you know what the difference is?

Yeah, your eth0:xx is just a label (a tag of sorts) attached to the entry. Otherwise, they're exactly the same thing.

You can even add an address with `ip addr add' that will be visible to ifconfig.

Re: There are real reasons for Linux to replace ifconfig, netstat, etc

#253
post #223
post #39

Earlier quoted context omitted.

The most underrated tool barely used outside of Windows sysadmin world.

In what capacity is Powershell something other than just another shell (of your choice)? Feela like Windows finally got a real CLI for API stuff - and O am glad this happened - but it's not really any different than csh, bash, zsh et cetera. A shell as a lower-level interface to your OS.

The main selling point of PowerShell is that you cannot save intermediate results of a pipeline to a file for inspection.

Re: There are real reasons for Linux to replace ifconfig, netstat, etc

#254

Earlier 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).

ip has a --json flag: https://github.com/CumulusNetworks/iproute2/commit/5df607725...

For the avoidance of doubt, this is not the official iproute2 repo.

This is the official one: https://git.kernel.org/pub/scm/network/iproute2/iproute2.git

Re: There are real reasons for Linux to replace ifconfig, netstat, etc

#255
post #58

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

TLDRRTFM of the day

"read read"?

Re: There are real reasons for Linux to replace ifconfig, netstat, etc

#256
post #250

Earlier quoted context omitted.

Kernel won, userland didn't.

It's not the first time I hear it, but what is it supposed to mean? Is there a single thing that can be called "linux userland"? Also, I doubt that someone combines Linux kernel with Windows XP userland. So in some regard all userland tooling running on the linux kernel might be considered "linux userland". If I understand the term userland correctly it is a term from kernel developers to say "this is code that doesn…

> Also, I doubt that someone combines Linux kernel with Windows XP userland.

That's Wine.

Re: There are real reasons for Linux to replace ifconfig, netstat, etc

#257
post #152

Earlier quoted context omitted.

> BSD's ifconfig isn't really related to Linux's ifconfig anymore because BSD has continued development and the Linux fork or version (don't remember which it is anymore) hasn't. There's a simple solution to the lack of maintenance on ifconfig: Maintain ifconfig. There's no need to break shit.

It's open source. Feel free. I'd expect there are significant architectural differences between Linux and BSD by this point, though, that would make it quite a challenge. Alternately, it might be like adding major new features to Xorg: possible but extremely challenging. My understanding is that the Linux version of net-tools was based on the BSD software, but I don't know how much code is actually shared between the…

> It's open source. Feel free.

I use BSD. And while I would send in patches for ifconfig, I haven't needed to. I have sent in patches for other things.

Re: There are real reasons for Linux to replace ifconfig, netstat, etc

#258

Earlier quoted context omitted.

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…

> Linux dropped the cost of using UNIX down to zero. BSD had already done that, better, and earlier. Let's not try to rewrite history.

Not true. AT&T claimed that the free versions of BSD violated their copyright on Unix with the result that even though anyone could download and install BSD at no cost, you never knew whether a court ruling would make your continuing to use it legally risky (at least if you want to use it in an enterprise or keep it connected to the net).

The legality of the free versions of BSD did not get resolved till there were many Linux users -- probably more Linux users than there were users of the free BSDs.

Re: There are real reasons for Linux to replace ifconfig, netstat, etc

#260
post #176

Earlier quoted context omitted.

MegaCLI (lsi hw raid control) sees your tc and raised you a few million awful flags.

I see your MegaCLI and raise you certutil: https://docs.microsoft.com/en-us/windows-server/administrati...

Oh fair enough but in the context of Linux command lines I think MegaCLI is genuinely one of the worst UX designs ever. Up until recently (post Balmer), Microsoft didn’t heavily emphasize the CLI for most things so a bad UX is not surprising.
Post reply on HN