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/
--
Preliminary Objectives
May 30, 2001
Kara J. Pritchard
Kernel
[2.3.4, 2.3.5, 2.3.14,
Obj 1 : Kernel Components
Utilize kernel components necessary to specific hardware, drivers,
system resources, and requirements. Includes implementing zImage and
bzImage kernel images, identifying stable and development kernels and
patches, and using kernel modules.
Includes tools and files such as:
* zImage
* bzImage
*
[2.2.1, 2.2.2, 2.2.7, 2.2.11, 2.2.12, 2.2.13, 2.3.9,
Obj 2 : Compiling Kernel
Properly compile a kernel to include (or disable) specific features
as necessary. Includes recompiling an existing kernel when needed,
implementing updates and noting changes in new kernel releases which
may affect your production systems, creating initrd, and installing
new kernels.
Includes tools and files such as:
* make
* /usr/src/linux/*
* /etc/lilo.conf
* make config
* make xconfig
* make menuconfig
* .config
*
[2.2.5, 2.2.8, 2.2.9, 2.2.10, 2.2.15, ]
Obj 3 : Patching Kernel
Properly patch a kernel to implement kernel updates, bugfixes, new
hardware support, and more. Implement kernel patches instead of
recompiling for new kernel versions. Properly remove kernel patches
from existing production kernels.
Includes tools and files such as:
* patch
*
[2.3.8, 2.4.1, 2.4.2, 2.4.3, 2.4.5, 2.4.7, 2.4.8, 2.4.10, 2.5.3, 2.5.4, 2.5.7, 2.5.8,
2.5.9, 2.5.10 ]
Obj 4 : Customizing Kernel
Patch, recompile, and reconfigure kernel options to customize kernel
for system requirements. Determine need for kernel compile versus
kernel patch. Build and configure kernel modules.
Includes tools and files such as:
* patch
* make
* /usr/src/linux
* /proc/sys/kernel/*
* modprobe
* /etc/conf.modules
* insmod
[2.3.13
Obj 5 : Debugging Kernel
Debug compiling problems, review error logs and configuration files.
Includes tools and files such as:
* /usr/src/linux*
*
2.2.1 Recompile the kernel when needed
2.2.2 Keep up to date on any changes in the kernel that could help your systems
2.2.5 Patch kernel source to add usb-support
2.2.7 Install a new kernel
2.2.8 Use 'patch' to udpate kernel to new version
2.2.9 Use 'patch' to apply fixes or features to current kernel.
2.2.10 Use 'patch' to remove or reverse a patch.
2.2.11 Create an initrd
2.2.12 Use make config whenever make xconfig or make menuconfig aren't available
2.2.13 Edit your .config file to make changes to kernel configuration manually.
2.2.15 You have kernel 2.2.08. Upgrade to 2.2.12 by patching making sure patch 09,
10, 11 have been installed.
2.3.4 Know when to use zImage versus bzImage
2.3.5 Know the difference between stable and development kernels
2.3.8 Make sure you know when to do a kernel upgrade and when to do a patch.
2.3.9 "Check to make sure your new image file is copied to where you want it.
(floppy, or where LILO wants it) "
2.3.13 When you get a compile problem, check all revisions of all software in
/usr/scr/linux-your_version_#/docmentation.
2.3.14 "Know the 4 classes of patches: Linus, AC, Subsystems (Serial, JFS, etc),
experimental. "
2.4.1 Disable unneeded kernel support
2.4.2 Rebuild kernel to modularize less needed support
2.4.3 Build an SMP kernel
2.4.5 Disable SMP support
2.4.7 Change the value of /proc/sys/kernel/* from the command line. (e.g.
ctrl-alt-delete, modprobe, version, etc)
2.4.8 Configure miscellaneous binary support. (e.g. Configuring kernel to know how
to execute Java class files)
2.4.10 Configure kernel to allow serial console. (used for debugging purposes)
2.5.5 Compile modules outside of kernel source tree (e.g. sound, PCMCIA)
2.5.7 Configure module options under /etc/conf.modules
2.5.8 Configure load path for modules under /etc/conf.modules
2.5.9 Force a module to load that's not compiled for current kernel
2.5.10 Know the relationship between 'modprobe' and 'insmod' and how each are used.
