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.

There are many concepts at LPIC-1, 2 and 3, not just at 2 or 3.  I
could see the case where something like machine-id could be at LPIC-1,
while LPIC-2 and/or LPIC-3 addresses deeper.

> 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).**

- bjs

**DISCLAIMER:  I'm biased because of negative feedback from major Red
Hat customers years ago (circa 2008-2009) when Red Hat started to use
UUID, I argued, and eventually won, the inclusion of the following
lines in all Fedora-based apps (which I wrote, eventually pairing it
down to 2 lines) ...

  # Accessible filesystems, by reference, are maintained under '/dev/disk'
  # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info


--
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

Reply via email to