Simone Piccardi <[email protected]> wrote: > I think there is a misunderstanding, I asked reasons for the removal of > ifup/ifdown, you answered telling now there is Network Manager and > proposing a way to disable an interface that does not work when that one > is DHCP configured.
Can you clarify this statement? I fear I'm reading this incorrectly. Just in case anyone doesn't know, understand the NetworkManager sevices (via API, nmcli, etc...) can bridge, create, disable, etc... interfaces on-the-fly. E.g., on systems that use "network-scripts" files, NetworkManager services modify these files. On systems that use "interface" files, there are many options, and even a newer facility for managing several. > If you have told me that you wanted to remove o reduce net-tools weight, > I could have understood better the point. > If you have told me you want to remove ifup/ifdown because now they are > only a Debian specific program (some time ago there were also some > scripts with the same name on RedHat, don't know it they are still > there) I could have understood better the point. Because so many people know only legacy scripts, Fedora (so, RHEL) updated ifup/ifdown to use "ip" commands years ago, and in more recent years, created a commandset "usernetctl" to interface into NetworkManager (possibly other systems). The scripts are still available in the "initscripts" package on Fedora. >> The LPIC is for Linux Users and Linux Professional (Linux Servers), in >> company, not use DHCP on more 95% of park machine, but static ip address >> setuped on network interfaces (interfaces, ifcfg-ethX, ensX, etc)... > So you propose also the removal of DHCP? I haven't seen a [true] PaaS solution yet that didn't use DHCP on SDN (software defined networking), let alone didn't build-up and tear down interfaces and even systems. As I mentioned before ... most services and any tools that are incompatible with handling stateless servers, and require persistent configuration on servers, are getting deprecated in favor of services and compatible tools that can do both. > My question was about the reasons to remove ifup/ifdown, if you want to > discuss removing the whole set of net-tools command ot the DHCP that's a > different question. Even then, we're talking legacy scripts that may or may not be updated, and aren't the "Greatest Common Denominator -- like tools like "ip", that are still compatible with newer developments. This is the difficulty LPI faces, legacy scripts that may or may not be updated, only included because of inertia and familiarity, but are still "static" and not very compatible with modern, Enterprise deployments. It's important people realize what was common in 2007 is likely deprecated for a reason in 2017, and only continues to exist because it's been hacked with commands and wrappers to newer tools for newer services, but likely isn't the most ideal tool. -- Bryan J Smith - http://www.linkedin.com/in/bjsmith E-mail: b.j.smith at ieee.org or me at bjsmith.me _______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
