Simone Piccardi <[email protected]> wrote: > Il 09/11/2017 21:28, Bryan Smith ha scritto: >> I don't have a Debian system in front of me, but if anyone wants to >> look, I suspect you will see scripts with "ip" commands as well. > > No, they are commands not scripts (package ifupdown) and are used to > bring up and down interfaces according to their /etc/network/interfaces > configuration. An interface should listed there to be managed by them.
Indeed I was correct. ifupdown uses "ip" CLI. Even the Debian package site confirms it depends on the iproute2 CLI package. [1] In fact, ifupdown2 (Python instead of shell) has been created to deal with the issues of the legacy ipupdown. [2] QUOTE: _"Like ifupdown, ifupdown2 is a high level tool to configure (or, respectively deconfigure) ..."_ The key here is that these are high level, legacy compatible, scripts that have been modified to try to support newer, dynamic services. And even ifupdown2 doesn't go far enough, while old ifupdown doesn't really do it at all. It's very, very important that people understand why many of these tools are being deprecated. They were designed for the days of net-tools, modified to support "ip" and newer facilities, but are still too limited. Tools that don't handle stateless servers are being deprecated for a reason. But that all aside ... High-level tools, especially legacy ones that are inflexible, will exponentially expand the number of topics that have to be covered. Simply put, if i saw someone in 2017 using ifup/ifdown, I'd have to warn them of the dangers of ever using those scripts. - bjs [1] https://packages.debian.org/stable/ifupdown [2] https://packages.debian.org/stretch/ifupdown2 -- 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
