On 2015-06-28 23:48, Ken Schneider wrote:
> On 06/28/2015 04:46 PM, licehunter wrote:
>> Those hardly look like insurmountable problems. I would have expected
>> people actually paid to work on this to be able to either make the
>> necessary changes to ifconfig, or rewrite it from scratch while
>> maintaining a compatible user interface. Not doing either is rather
>> unprofessional.
>
> And where do you read that the people working on openSUSE, or other
> distributions of linux, are are all paid professionals? They’re not!
> Most are just plain folks volunteering their time. And it has been
> announced for over a year that ifconfig was going to be dropped.
That’s right. If somebody had actually paid to support those tools, they
would have been repaired long ago, assuming it were possible.
> I should also like to mention that there is a difference between
> something being no longer maintained or supported (i.e., deprecated),
> and forcefully removing it from a working system.
As I explained on another post, this was made intentionally, and I
explained why. And it was an announced move.
On 6/27/2015 5:56 PM, deano ferrari wrote:
>
> Ranting about it here in a help forum is pointless. It’s not recent news
> anyway, and it’s not specific to openSUSE, or any other distro for that
> matter.
>
> http://tinyurl.com/37ynga4
>
>
RHEL has published a short “Cheat Sheet” for the ip command.
I have never used “ifconfig eth0 up/down” in my life (and I’m using Linux as my primary/only OS since over 12 years).
What’s wrong with “ifup eth0” and “ifdown eth0”? That’s shorter and simpler, too…
I have to admit that I am (still) using “ifconfig” for a quick overview of the interface status though.