The static network file/script approach, just like static firewall file/script approach, is largely dying or dead because of software defined infrastructure. They fail to be dynamic, use message passing and otherwise provide notifications to other services. Peer service awareness is still UNIX-like, despite rhetoric. That's why there are different services that work together, each doing one thing, and leverage the pre-existing kernel, message bus and other solutions, instead of being ignorant of system state. **
Whether static files still belong at the LPIC-1 level should, indeed, be up for debate in the next set of objectives. I'm not saying either way, but I would put my foot in the door and say it should at least he visited. -- bjs **P.S. The only time I ever configure static files is when I must configure Clevis with Dracut plug-ins for Tang, along with GRUB (kernel boot parameters like rd.neednet=1 and rd.luks.uuid). E.g., https://github.com/BJSmithIEEE/elmedia0/blob/main/default/ks/include/ks-elX-90pst-clevis_common.inc On Wed, Nov 27, 2024, 08:48 Michael Gisbers via lpi-examdev < [email protected]> wrote: > Hi Bruno, > > On 27.11.24 14:21, Bruno Santos via lpi-examdev wrote: > > Hi all. > > I'm reviewing some LPIC-1 materials and it strikes me that the 109.2 > > Persistent network configuration topic still speaks of > > /etc/network/interfaces when modern distributions, for some time now, > > no longer provide that file . > > it is no matter how old an system is. It just depends on the network > configuration tools you - or the distribution - use. > > > > > Fedora no longer has the network directory in /etc and Ubuntu (I'm > > assuming also Debian - didn't check), still has the directory, but no > > longer the file exists. > > Like Harald already pointed out on Debian 12 it is still present. > > And also Proxmox (which is no old distribution) using a Debian 12 base > is using that file for their network configuration. > > You might also use other network config tools like systemd-networkd or > NetworkManager on your distribution if they are provided. > > It's on you choosing what you like most and what fits your needs. > > > > > I know that NetworkManager exists and tools like nmtui and mncli do > > all the work, but isn't it time for LPIC to update itself ? > > I'm reading the Learning Materials v5.0 provided by LPI on their website. > > Those Learning Materials fit for the actual exam which is also available > in v5.0. That means the materials have to cover the exam objectives. > > With changes in the objectives and new exam version there will be > changes in the learning materials. > > > > > I'm sure other distros still provide those files and on Fedora we can > > still install (not more recent versions) network-scripts package , but > > how can a student practice if those files are no longer available ? > > The tools are available, but they don't have to be the preselected in > your distribution. To study for LPI sometimes mean to also have a look > on other distributions to get an overall view. > > I - for my part - would find it quite hard to try apt-get/dpkg package > management on Fedora or using zypper/rpm on Debian. > > -- > Regards, > > Michael Gisbers > http://gisbers.de > > GnuPG Fingerprint: DD12 A30E 5070 68C7 B405 C18E D51C 8A53 63B4 835B > GnuPG PublicKey: http://tinyuri.de/mgisberspub > > _______________________________________________ > lpi-examdev mailing list > [email protected] > https://list.lpi.org/mailman/listinfo/lpi-examdev -- Sent from my phone, apologies for any brevity as well as autocorrect Bryan J Smith - http://linkedin.com/in/bjsmith
_______________________________________________ lpi-examdev mailing list [email protected] https://list.lpi.org/mailman/listinfo/lpi-examdev
