5 ms·
Your comment doesn't make sense. Why is it good to know that a command that you haven't even heard about is phased out? Fwiw you don't need to be a sysadmin to
by isatty 9y ago
Your comment doesn't make sense. Why is it good to know that a command that you haven't even heard about is phased out?
Fwiw you don't need to be a sysadmin to have known of ifconfig. Hell how is it possible to have set up networking on Linux distributions without knowing this command?
- shaklee3 9y agoI think he means he hadn't heard about it being phased out.
- mathw 9y agoMmm. I had no idea either. I was surprised to see how old the linked article is! I'm not a sysadmin, but I use Linux every day. Just can't keep up anymore...
- pnutjam 9y agoI'm a sysadmin and I hadn't heard this until last year. It explains why only root can do an ifconfig on SLES, but anyone can run 'ip a'
- shmerl 9y agoIn Debian both of them sit in /sbin so it boils down to whether /sbin is in the PATH by default. I think it better should be, rather than not.
- keithpeter 9y agoEnd user here: I found out about all this when I installed Debian 9 with the lxde desktop. Lxde brought in WiCD for wifi, which is fine, except when attempting to connect in a location with a very large number of Wifi connections available (anything over 70 different ones) it would not connect. Further investigation revealed a 'too much output' error from the iwlist scan command (this is from memory). Worked fine at home and in most of my usual 'third space' locations of course because way less than 70ish connections. Booting into a live USB with network-manager on it and googling lead to my discovery of the depreciation.
- shmerl 9y agoI know about the command and use it. But I've never heard about its deprecation.