@nixCraft@mastodon.social
You know you're an old school Linux user when... you still try to use ifconfig and get a "command not found" error, followed by a moment of silent grief π€¬![]()
You know you're an old school Linux user when... you still try to use ifconfig and get a "command not found" error, followed by a moment of silent grief π€¬![]()
@nixCraft@mastodon.social Is it even "old school"? The switch was pretty recent.
I still don't understand why the forced switch though. ifconfig was simpler and clearer. I don't understand why we can't have both available though. It isn't as if either is particularly huge... (Obviously excluding embedded setups like Busybox where every kilobyte counts potentially.)
As others have said, the syntaxes for ip are just confusing.
@nixCraft@mastodon.social Which Linux distros do not have ifconfig? It is included in every platform I run.
@nixCraft@mastodon.social rpm -Uvh net-tools-deprecated
usually fixes the issue.
@nixCraft@mastodon.social But you're truly cursed only if you accidentally type ipfwadm.
@nixCraft@mastodon.social luckily I moved on, and use ip addr instead
@nixCraft@mastodon.social It still exists! Just apt-get/yum/dnf install net-tools.
@distrowatch@mastodon.social @nixCraft@mastodon.social Debian Bullseye does not have it by default - not sure about earlier releases.
@jaark@infosec.exchange @nixCraft@mastodon.social Really? Because my Debian 12 Bookworm still had ifconfig installed by default with a fresh install. I think Debian 13 "Trixie" is the first I've encountered that did not have ifconfig by default.
@distrowatch@mastodon.social @nixCraft@mastodon.social Odd - I don't recall doing anything special when I created my bullseye vms .. other than getting annoyed that I had to learn new commands like 'ip' and 'ss'