Hi guys, thanks for the ifup/ifdown deep dive :) It was super interesting; but it left me with the very same question most of you mentioned: What should LPI do?
As an important aid to bring your arguments into our objective proposal, I want to stress three observations: * We should decouple the discussion of net-utils, ifup/ifdown and NetworkManager * We should think in levels of tools, in that case runtime configuration (net-utils, iproute2) and persistent configuration (network-scripts/interfaces, ifup/down, nm, systemd-networkd). We might also call them low and high level tools. * Within each level, we should think in generations of tools (e.g. net-utils vs. iproute2 or ifcfg-* vs. nm) Sorting your arguments (sorry for shamelessly reproducing them here!) might lead to these proposals: * net-utils are superseded by iproute2. We should focus on iproute2. Since candidates might still come across the old tools, we might want to lower net-utils to awareness level and ask candidates to know that ifconfig and route exist, without requiring them to actually know the exact syntax. Instead, we should be explicit about using iproute2 for any runtime configuration and debugging in 109.2 and 109.3. * The old generation of persistent network configuration used to be different for each distribution family. Therefore we used to only cover ifup/ifdown which seemed to be the common utility working on all distros, one way or the other. Given that legacy systems are still around, knowledge of ifup/ifdown might help candidates facing these systems. While it might not be absolutely ideological correct, it certainly is pragmatic. And, there is not a lot to know about these tools *if you want to use them* -- although I have the feeling this is not entirely true if you want to *discuss* them :D What about keeping ifup/ifdown for now and flag them for removal in the following objective update? * With nm and maybe systemd-networkd, there is a new generation of network configuration tools available. These tools provides a common mechanism for persistent (Bryan: I also mean persistently enabling dynamic configuration on servers/IaaS instances) configuration. Given the current distribution support, this would mean including NetworkManager and nmcli as well as awareness of systemd-networkd (and maybe awareness of netplan?) in LPIC-1. Focus should be both servers and desktops/laptops. To avoid too much change to the objectives, I recommend keeping the structure of 109.2 and 109.3 as it is for now. In case we add NetworkManager to 109.2, that objective would turn more into a configuration topic focusing on high level tools while 109.3 would focus more on using iproute2 to debug and work with the runtime configuration. Given that we drop SQL from 102, we would have one spare weight point to spent which we could use to compensate NetworkManager in 109.2 (for those who are curious where the second point went, I want so suggest adding it to GPG since we will agreed to add some more stuff here). I know this is a controversy topic; one might likely come to different conclusions that those I pointed out here. However, I think they somehow respect all the arguments shared in the discussion. What do you think? Fabian PS: I don't think there is a general hard rule what to include / not to include in the exams. Considering minimal installs is helpful, but not sufficient. There are practical and didactic aspects which we should take in consideration, too. You've pointed out a lot of them during the discussion; that was really great and illustrated that we need these discussions instead of just applying static rules. Thanks again :) On Thu, Nov 9, 2017 at 1:02 PM, Alex Clemente <alexbm...@gmail.com> wrote: > Dear, > > The topic abouve, is very important for SysAdmin, considerat keep again. > > 109.2 Basic network configuration: > * Drop ifup > * Drop ifdown > > 109.3 Basic network troubleshooting: > * Drop ifup > * Drop ifdown > * Consider whether or not we should keep the dedicated IPv6 tools such as > ping6 since functionality seems to get merged in the same tools again > > 2017-11-09 9:33 GMT-02:00 Fabian Thorns <ftho...@lpi.org>: > >> Dear all, >> >> thanks for the great discussions on the LPIC-1 exams. Since the >> discussion seems to settle, it's (almost :) time to wrap things up. Before >> doing so, I'd like to share a list of additional proposals which were >> brought up in side conversations or seem worth a look for various reasons. >> >> Since they haven't been discussed in this thread yet, it would be great >> to get your thoughts on those, too. >> >> 105.1 Customize and use the shell environment: >> * Move lists to 105.2 >> >> 105.2 Customize or write simple scripts: >> * Turn "sh" into "Bash" in "Use standard sh syntax (loops, tests)." >> >> 106.3 Accessibility: >> >> Here we got two proposals: >> >> * One to only address color blindness and reduced debility of sight be >> covering color adjustments/inversion (using xcalib), zoom in/out, desktop >> themes, as well as voice recognition. >> >> * The second proposal is to drop this section since installing these >> tools for only one weight seems unreasonable to some trainers >> >> 107.2 Automate system administration tasks by scheduling jobs: >> * Add systemd.timer >> * Remove anacron >> >> 108.2 System logging: >> * Drop syslogd >> * Add rsyslogd >> * Add interaction between rsyslog and systemd-journald >> * Add systemd-cat >> >> 109.2 Basic network configuration: >> * Drop ifup >> * Drop ifdown >> >> 109.3 Basic network troubleshooting: >> * Drop ifup >> * Drop ifdown >> * Consider whether or not we should keep the dedicated IPv6 tools such as >> ping6 since functionality seems to get merged in the same tools again >> >> 109.4 Configure client side DNS: >> * Add awareness of systemd-resolved >> >> 110.2 Setup host security: >> * Add systemd.socket >> * Drop inetd (but keep xinetd) >> * Drop TCP wrapper >> >> 110.3 Securing data with encryption: >> * Add additional SSH ciphers >> * Add gpg-agent >> * Add gpg options to encrypt, decrypt, sign and verify files >> >> Let me know what you think! And don't worry about 101, there will be a >> similar mail soon :) >> >> Fabian >> >> On Tue, Oct 10, 2017 at 10:10 PM, Fabian Thorns <ftho...@lpi.org> wrote: >> >>> We might want to start commenting on exam 102 here. >>> >> >> >> _______________________________________________ >> lpi-examdev mailing list >> lpi-examdev@lpi.org >> http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev >> > > > > -- > > -- > Alex clementea.clementesi...@uol.com.bralexbm...@gmail.com > Analista Linux, Unix, Virtualização e Middleware > Instrutor Linux e Open Source > ----------------------------- > AWS Technical Professional > Azure Datacenter in Cloud Platform for Technical > CompTIA Linux+ Powered by LPI > SUSE 11 Certified Linux Administrator > SUSE 11 Technical Specialist > LPIC-1 Certified Linux Administrator > LPIC-2 Certified Linux Engineer > > > _______________________________________________ > lpi-examdev mailing list > lpi-examdev@lpi.org > http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev >
_______________________________________________ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
