102
Deprecated Linux Commands You Should Not Use Anymore
(itsfoss.com)
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
The thing about these deprecated tools is that the replacements either suck, are too convoluted, don't give you the same info, or are overly verbose/obtuse.
ifconfiggave you the most relevant information for the network interfaces almost like a dashboard: IP, MAC address, link status, TX/RX packet counts and errors, etc. You can get that withipbut you've got to add a bunch of arguments, make multiple calls with different arguments, and it's still not quite whatifconfigwas.Similarly,
iwconfiggave you that same "dashboard" like information for your wireless adapters. I useiwto configure butiwconfigwas my go-to for viewing useful information about it. Don't get me started on how much I hateiw's syntax and verbosity.They can pry
scpout of my cold dead hands.At least
nftablesis syntax-compatible.scpthe command isn't deprecated, but the SCP protocol is. The command internally uses the SFTP protocol (with OpenSSH 9+)ref: OpenSSH SCP deprecation in RHEL 9: What you need to know
rsync is one of the most beautiful pieces of software ever created.
I always thought that scp was more secure than rsync. I remember back in the day when I "graduated" to scp from rsync. So in reality, did I regress?
I just do
ip a. It doesn't show packet counts or errors, but it has everything else and more.The "and more" part is the problem for me.
I got used to
ip --br arecently.ip -br a, evenI miss ipconfig. I had to make an alias just for it that I load up on new machines because its part of the muscle memory.