Has this come up? Most people know slice/filesystem by partition and slice/filesystem by label. But are we covering slice/ filesystem by UUID in new objectives?
It's been in the kernel for several, major versions now (since 2.2 IIRC). GRUB and other bootloaders support it. Virtually all init processes support it. And now many distros are starting to change to it by default -- Fedora (and forthcoming RHEL releases), Ubuntu, etc... If you open up your /etc/fstab and other files, you'll see UUID. Why? Many enterprises have issues with dynamic device as well as conflicting labels (which may be blank since they are "optional," unlike UUID), especially across various storage. The UUID solves this. Just curious if we have an objective, or at least an "exam writing note" that covers these concepts. This is one of the #1 issues I've been running into with junior administrator. Many of them complain about it. Even some "old dogs" do. As usual, a few others accuse it of being "Red Hat stupidity" but Ubuntu and others are doing it as well (for the same reasons as Red Hat). Just thought I'd mention it, since I ran into it again the other day. -- Bryan J Smith Professional, Technical Annoyance [EMAIL PROTECTED] http://www.linkedin.com/in/bjsmith -------------------------------------------------------- I don't have a "favorite Linux distro." I use, develop and support community efforts, often built around Linux. Technology and solutions are my focus, not dragging in assumptions, marketing and other concepts which dominate non-community developed software, which I left long ago. _______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
