On Tue, 5 Dec 2017 at 23:04:10 -0500 Bryan Smith <[email protected]> wrote:
> Alessandro Selli wrote: >>>> dbus: machine-id, session.conf, system.conf >>>> I see it very often that admins do not understand the role of the >>>> machine-id when cloning VMs. >> >> This could be a reason to have them in LPIC-304, Virtualization (if they >> are not there already). But why in LPIC-1? > > Depends. A lot of junior admins deal with recent builds. Initial > investigation and basic identification of a probably cause can be a > junior admin responsibility, at least from an initial troubleshooting > aspect. True, however, as there is nothing about virtualization in LPIC-1, a junior sysadmin's troubleshooting responsibilities concerning VMs are out of the picture. Are there other aspects of basic system admnistration that are impacted by these files? [...] >> What should an LPIC-1 candidate know about it? I cannot see anything in >> /etc/pam.d/polkit-1 and /etc/polkit-1/rules.d/50-default.rules a sysadmin >> might need to customize in a typical environment. >> Concept of UUID and it's use is already in LPI-201: >> Topic 203: Filesystem and Devices >> 203.1 Operating the Linux filesystem >> Key Knowledge Areas: >> Use of UUIDs for identifying and mounting file systems >> Why moving it into LPIC-1? > > Yeah, this is a tough one. > > I, for one, wish everyone knew about about both 'lsblk' (which just > reports what is already in /sys/block, and doesn't require root) and > 'blkid'**(which requires root, as it queries block devices directly), > in addition the kernel device mapper already already pre-creating > various links under /dev/disk/. > > We all see the need for detail in LPIC-2, but I also could understand > an argument for LPIC-1. There's not a Fedora/RHEL system out there > that doesn't have at least one (1) UUID reference these days for the > ESP (/boot/efi) and/or Boot (/boot).** I did notice /etc/fstab shows up both in 101 (104.3 Control mounting and unmounting of filesystems) and in 201 (203.1 Operating the Linux filesystem). I don't think fstab is such a complex file to deserve double coverage, an introductory one in 101 and an in-depth one in 201. I think fstab should be considered prerequisite knowledge in 201 and that it should be explicitly mentioned in 101 only. lsblk is simple and useful enought tool to deserve a mention, but then several other util-linux commands are too: lslogins, findfs, partx, fsfreeze, runuser, rename, prlimit, nsenter, namei, mountpoint, delpart, chcpu ... Aren't we overstuffing the already overloaded exam? Alessandro _______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
