While surfing the border between L1 and L2 test objectives, I stumbled
over a few things; my report may be a bit late, but since the objectives
apparently are still in draft:
* Now what are the proper Objective ID's?
I had a big fight with Kara over a comprehensive ID scheme, where
specifying the area IDs was the main stumbling block. I thought we
settled on the scheme as is currently on-line at
http://www.lpi.org/cgi-bin/poms.py , and I re-numbered all L1
objectives to comply with this. I also followed this scheme when I
put the first drafts of the L2 objectives online. However, Kara changed
them to something else for the latest drafts last month. Moreover, the
areas appear in random order.
If L2 is not following a generic scheme there is no point in upsetting
everybody by changing all the L1 ID's. Most importantly, everybody
now will get confused anyway because objectives with numbers like
"2.4.1" have esisted in the current L1, and now also in L2. The area
numbering currently in POMS was meant to avoid this situation and offer an
expandable unique objective numbering scheme.
So I really think the L2 objectives must be re-numbered (and listed into
some logical order).
* In the various objectives on hardware (esp. 2.4.4 "Adding New
Hardware"; 2.4.3 "Software and Kernel Configuration") I find no mention of
the understanding and use of the /dev/ system, the new device files (err,
what is it called again?), or the use of MAKEDEV .
* lsdev (mentioned in 2.4.2 "Adding New Hardware" and 2.13.5 "General
Trouble Shooting") is not universal, maybe a Red Hat ideosyncracy?
* There are frases like "mount/umount" and "swapon/swapoff" (in 2.2.1
"Operating the Filesystem") that use the directory separator to separate
different commands: this is confusing, especially since these frases occur
in lists with full paths to files. Please use something else to separate
commands, for instance a comma ',' !
--
Tom Peters
Director of the Board & Exam Development Specialist,
Linux Professional Institute
e-mail: [EMAIL PROTECTED]
--
This message was sent from the lpi-examdev mailing list.
Send `unsubscribe lpi-examdev' in the subject to [EMAIL PROTECTED]
to leave the list.
