Les Bell has taken more time to develope the preliminary System
Customization objectives. He has reviewed the task list for completion,
filling in gap in the current task list and implementing them into the
objectives. His files are attached.
Please review and comment as previously requested :)
Thank-you Les!
-Kara
---------- Forwarded message ----------
Date: Mon, 4 Jun 2001 12:45:34 -0500 (CDT)
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Preliminary Kernel Objectives
In order to assist in speedy objective development, I've tried to start
developing some preliminary objectives for our tasks, based on the most
recent organizational structure. (I've only received one response to the
last thread on organizing!)
The objectives are definitely not complete in current form, nor are they
the concrete foundation we're forced to work with. The tasks are our
foundation (also attached). The goal is to create objectives which cover
these tasks and fill in the technical gaps and details.
Our Level 1 objectives
(http://www.lpi.org/http://www.lpi.org/p-obj-101.html and p-obj-102.html)
should provide a good outline for what form and style objectives should be
written in. I've modified slightly (including bullets for specified files
and tools covered) but the rest should be developed in the same fashion as
the current Level 1 objectives. There's no need to obsess over this step
at this stage, as I plan to have this completed in a stage of formal
review.
I would like either comments, changes, and additions as well as assistance
completing (technically) the objectives I've posted; your comments and
submissions for replacement or additional objectives; and your comments
for supplementary objectives (if any).
Please begin by reviewing the current objectives for Level 1 at the URLs
listed above. Next review the task file for this group. Finally, review
the preliminary objectives file and comment. Please note that the
preliminary objectives file associates the current task numbers with the
affiliated objective. Please continue to refer to these task IDs when
commenting, reorganizing, etc. objectives.
I will continue submitting preliminary objective files for various
categories today and tomorrow. I would like good discussion and progress
toward finalizing objectives in progress by Wednesday. By Friday, those of
you interested in the contract positions to finalize objectives should be
able to begin review. By next week, I would like to publish our objectives
for public review and begin collecting preliminary items.
The next 10 days are going to be crazy, and I greatly appreciate your time
and dedication to development. We are moving extremely quickly, and
everyone is very excited about our current developments!
Please contact me if you are available 6/8 - 6/12 for contract objective
review and development. I apologize that this will encompass a weekend,
but it is necessary for succeeding with our current development schedule.
Slots are filling for the Item Writing session planned for the week of
June 18. If you had hoped to participate in this event, please contact me
to discuss availability, expenses, etc. It is likely that a two team
approach (6/18 - 6/20, 6/20 - 6/22) will be used, allowing for flexible
travel arrangements.
--
Kara Pritchard Phone: 618-398-7360
Author, RHCE Exam Cram
Director of Exam Development http://www.lpi.org/
Site Manager http://www.LinuxUsersGroups.org/
--
1.7.1 Write Perl scripts, using regular syntax and including modules where
necessary.
1.7.2 Use Perl's taint mode in Perl scripts to increase security.
1.7.3 Install new Perl modules from CPAN using the CPAN module
1.7.4 L1 Use sed in a script to do regular expression substitutions.
1.7.5 L1 Use awk in a script to split data into fields
5.1.1 Write script for check if any server go down and setup automatic
notifications by way of pager or other means.
5.1.2 Write cron scripts that parse log files for specific alerts and email
the entries to a specific address
5.1.10 Write a script that notifies you when specific users login and logoff
5.2.15 Write cron scripts that use rsync to maintain file synchronization
across machines
6.2.6 Write a script to monitor various files and services and email you
when there are errors.
System Customization Objectives
Objective: Use scripts to automate tasks
The candidate should be able to: Write simple Perl scripts that make use
of modules where appropriate. Use the Perl taint mode to secure data.
Install Perl modules from CPAN. Use sed and awk in scripts. Use scripts to
check for process execution and generate alerts by email or pager if a
process dies. Write and schedule automatic execution of scripts to: parse
logs for alerts and email them to administrators; synchronize files across
machines using rsync; monitor files for changes and generate email
alerts.Write a script that notifies administrators when specified users
log in or out.
Includes tools and files such as:
* perl -MCPAN -e shell
* bash, awk, sed
* crontab
