On Thu, Jun 20, 2013 at 4:14 PM, Alessandro Selli <[email protected] > wrote:
> Aren't there already several plain awareness areas? > Actually, that's the question for Exam Writers under Bloom's Taxonomy. I think we were just giving "examples" of potential questions as nothing more than "examples." But that's not our role. For the Objectives, I think we're limited to "inclusion" or not. But Matt should feel free to correct me or not. ;) This is an different matter. Of course you know this does not > accomplish the same thing as the chattr command does: a directory > permissions affects *all* files inside the directory. My only point is this ... "real world scenario" (see it constantly) ... "More experienced Linux user doesn't like the fact that the 'official IT department' has taken away root from him. But before he 'gives it up' (or possibly after using a loophole in security, a command/access allowed by policy**), he puts immutable on several files, especially non-supported/older binaries/libraries (especially those that allow him access as root again) so they cannot be replaced by IT department updates. New Linux sysadmins cannot figure out why some updates are failing and/or how the system doesn't match other systems, etc... (suspecting he still has root)." bjs: "Humour me, run 'lsattr' on the binaries in the package failing to update" sysadmin: "lsattr? What's that do?" I kid you not when I see this _constantly_. ;) -- bjs **NOTE: One of the many reasons I don't like sudo, or more directly, I'm extremely critical of /etc/sudoers lines and regularly reject many of them. ;) -- Bryan J Smith - Professional, Technical Annoyance b.j.smith at ieee.org - http://www.linkedin.com/in/bjsmith
_______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
