ifconfig
!!! I think ip has replaced it.I think they're both available. But the newerI noticed on some newer Linux distros that they no longer useifconfig
!!! I think ip has replaced it.
Looking at FreeBSD's ifconfig() makes you realise just how powerfull/feature rich it is. Makes you wonder if anyone uses more than 5% of its capability
ip
is recommended.I think they're both available. But the newerip
is recommended.
Don't know about that. On MX Linux 18.3 I have both of them preinstalled.
Looks like you specifically need to install it.
ip a
and all that jazz. ifconfig
and their sysV init is very similar to ours.Almost forgot, MX Linux is also based on Devuan. It's the reason why I've bothsystem-d distro's useip a
and all that jazz.
Devuan usesifconfig
and their sysV init is very similar to ours.
ifconfig
and ip
available 'ifconfig' was already slowly being replaced by 'ip' long before systemd existed.Again shows the grubby tentacles of systemd everywhere in the OS with most Linux distros.
ifconfig if0 inet ... up
.Unless it's a wireless interface, then you need to usebut basic usage stays the same
iwconfig
. Or a bridge and need to use brconfig
. Need VLANs? Then you need yet another command. It drove me bonkers, they're all network interfaces for crying out loud. Unless it's a wireless interface, then you need to use iwconfig. Or a bridge and need to use brconfig. Need VLANs? Then you need yet another command. It drove me bonkers, they're all network interfaces for crying out loud.
dladm
to do all the *datalink* configuration (and I like the distinction). ifconfig
just matches better with the Solaris kernel because, like FreeBSD, it's a complete OS. So the userland tools are perfectly matched with the kernel and its capabilities. With Linux there's a kernel, period. And you need a bunch of tools from other projects to make it work. Because they're separate projects the tools and the kernel never quite match up.Because they're separate projects the tools and the kernel never quite match up.
I like Linux over FreeBSD. Because there's no base nor ports. Packages will use the openssl from the openssl package but not the openssl of the system. Get rid of a lot of problems.That's one of the main reasons I really like FreeBSD over other systems. Things are a lot more seamless the way FreeBSD is developed. I think it's one of the big failings of a purely "bazaar" model.
I like Linux over FreeBSD. Because there's no base nor ports.