3 ms·
> or even before they fully understand the old thing. I feel that /sbin/ip is in almost every way a better tool than /sbin/ifconfig, is that not the concensus
by akira2501 7y ago
> or even before they fully understand the old thing.
I feel that /sbin/ip is in almost every way a better tool than /sbin/ifconfig, is that not the concensus?
> Linux introduced a very complicated new API.
Which highlights the fact that the moment you want to have in-depth interactions with a driver for a piece of hardware ioctls are the wrong choice.
OSS was great if you had exceptionally simple needs.. the moment you want to do "professional" audio it was a nightmare. ALSA is _somewhat_ better for this, and I honestly wish they went with a more netlink(3) style API instead of an IOCTL driven one.
What's the point of pantomiming the old thing when the old thing wasn't designed properly in the first place?
- zymhan 7y agoMy opinion is that `ip` is a more powerful tool, but it is not as useful for quickly obtaining information or performing a basic action like up/down.
- tssva 7y agoMy opinion is that while a little more verbose it is just as useful for obtaining information or performing basic actions. Especially since it allows you to use the same cli and actions to maintain most network related actions rather than multiple tools with varying commands.
- jeltz 7y agoAnd my opinion is that ip is easier to use in almost every way than ifconfig. The man page used to be bad but the tool has always been easy to use as long as I remember.
- iso947 7y agoIfconfig wins on the following 1) name. It’s to configure the interface 2) default format. Far better spaced than “ip”’s various outputs. I find “ip -o a” just about manageable, but if config shows data far more cleanly imo