|
Totally agree on merging the two capacity management topics. I say: award 1 point to 201.1 "Kernel components" and one to 211.3 "Remote e-mail" These are topics that require a good deal of preparation by the student so they should get that back with a heavier share on the exam. To my horror I discover LILO indeed is in 202.3 again.... How many percent of Linux systems on-line today are running it? Why can't we ever say goodbye to OLD features of Linux in the exams.... Can anyone please tell me how a student must prepare for the LILO part of the topic, as I do not know... Kind Regards, Reinier On 12-6-2013 14:11, G. Matthew Rice
wrote:
On Wed, Jun 12, 2013 at 4:30 AM, Marc Baudoin <mbaud...@linagora.com> wrote:weight of 10 points is more than it deserves. Objective 200.2 doesn't list a single command so it seems very similar to 200.1 (troubleshooting often begins by measuring). Shouldn't these two objectives be merged as the former 213 objective has been merged into other relevant objectives?Hi Marc,I agree and think that we could merge 200.1 and 200.2 (make it a weight of 6). They are quite related, as you say. One focuses on measuring, the other on identifying the problems. Where to put the 2 extra weights, though? I'd recommend 1 to 'alternate boot loaders' (now that it includes lilo) and 1 to 'predict future resource needs'. ... --
|
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
