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.
True we need to moved sensibly but not glacially. If (for example) BASH 3.0 takes off like wildfire and the new features are like mana from heaven, then we would look silly still testing an older version. Note that I don't think this is likely.
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.
It has to be more than just the LSB. From my reading, the LSB doesn't mention BASH (or csh, or ksh) except in the way BASH interacts with certain glibc functions. The LSB only notes that SH needs to be available and where it should be located in the file structure.
Even so, we need to produce a roadmap for the community that details the speed at which we would implement such changes.
This is what my query was hoping for.
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.
Another excellent example of something outside the LSB.
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.
Or how to enable it if there is a valid reason to use it and do they know THAT?
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.
A process to compare the rapidly changing world of Linux to our existing job task analysis would be useful. For example, are the changes to BASH that prompted my thinking really relavent to a junior sysadmin or is it a more senior thing?
As a project lead I would like to know when I need to change such things and what process those changes need to follow to be implemented and accepted in the community.
Mark Miller Level One Project Lead _______________________________________________ lpi-examdev mailing list [EMAIL PROTECTED] http://list.lpi.org/mailman/listinfo/lpi-examdev
