[...]-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Just my $0.02:
A certification program such as LPI's is essentially a skills standard, and as such we have a responsibility to move slowly and cautiously on what is included in this standard.
If anything, we need to be vigilant that the LPI program matches LSB-mandated tools and versions. When LSB publishes release 2.0 -- now in a late beta version -- LPI should determine any changes involved in having the LPIC program match the revised LSB standards. Even so, we need to produce a roadmap for the community that details the speed at which we would implement such changes.
Agreed.
But there are many areas where we have to create additional standards. Especially in security basics we need to present state of the art knowledge.
For example distributions begin to disable tcp for the X server by default. Candidates need to know about the "-nolisten tcp" parameter and how they can secure their X server even with enabled tcp.
Maybe we should start to collect relevant changes and thoughts even before a job task analysis is initiated, i.e. a structured skill objectives document which will be backed up by the JTA later.
-- Torsten Scheck <[EMAIL PROTECTED]> Jabber:[EMAIL PROTECTED] GnuPG 1024D/728E 6696 F43D D622 78F1 F481 45C0 2147 69AB DD54 software engineer:open standards/access/knowledge:enthgnusiast _______________________________________________ lpi-examdev mailing list [EMAIL PROTECTED] http://list.lpi.org/mailman/listinfo/lpi-examdev
