David Downey has spent the time to develop the preliminary troubleshooting
objectives. His files are attached.
Please review and comment as previously requested :)
Thank-you David!
-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/
--
Objectives (Troubleshooting)
[3.34.1, 3.34.2]
Objective: Recovery disk creation
Candidate should be able to: create both a standard bootdisk for
system entrance, and a recovery disk for system repair
Includes such tools as:
* /usr/sbin/rdev
* /bin/cat
* /bin/mount (includes -o loop switch)
* Any standard editor
* /sbin/lilo
* /bin/dd
* /sbin/mke2fs
* /etc/fstab and /etc/inittab
* /usr/sbin/chroot
* Familiarity with the location and contents of the LDP
Bootdisk-HOWTO
(http://www.ibiblio.org/pub/Linux/docs/HOWTO/Bootdisk-HOWTO)
[3.34.2]
Objective: Be able to identify all boot stages such as boot loader, kernel,
hardware, software
Candidate should be able to: determine, from bootup text, the 4 stages
of boot sequence and distinguish between each.
This includes:
* boot loader start and hand off to kernel
* kernel loading
* hardware intializiation and setup
* daemon initialization and setup
[3.34.3]
Objective: Be able to recognize and diagnose lilo boot failures utilizing lilo
error codes
Candidate should be able to: determine specific stage failures and
corrective techniques
This includes the following knowledge and files:
* Know meaning of L, LI, LIL, LILO, and scrolling 010101 errrors
* Know the different LILO install locations, MBR, /dev/fd0, or
primary/extended partition.
* /boot/boot.b
* Know significance of /boot/boot.### files
[3.34.4, 3.34.5, 3.34.6]
Objective:
Be able to recognize and identify boot loader and kernel specific
stages and utilize kernel boot messages to diagnose kernel errors. Be
able to identify and correct common hardware issues. Be able to
determine problem owner, hardware or software.
This includes:
* screen output during bootup
* /bin/dmesg
* kernel syslog entries in system logs (if entry is able to be
gained)
* various system and daemon log files in /var/log/
* /sbin/lspci
* /bin/dmesg
* /usr/bin/lsdev
* /sbin/lsmod
* /sbin/modprobe
* /sbin/insmod
* /sbin/modprobe
* /bin/uname
* location of system kernel and attending modules
/, /boot, and /lib/modules
* /proc filesystem
[3.34.7, 3.34.8]
Objective: Be able to identify, diagnose and repair local system resource
configuration.
Be able to identify, diagnose and repair local system environment.
This includes the following file locations
* /etc/profile && /etc/profile.d/
* Core system system variables (aka $PATH, ect ect)
* /etc/bashrc (or other appropriate global shell configuration
files)
* /etc/init.d/
* /etc/rc.*
* /bin/ln
* /bin/rm
* Any editor of choice
* /etc/ld.so.conf && /etc/ld.so.cache
* /sbin/ldconfig
* /sbin/sysctl && /etc/sysctl.conf
[3.34.9, 3,34.10]
Objective: Be able to identify and correct common network setup issues to include
knowledge of locations for basic configuration files and commands.
These include:
* /sbin/ifconfig
* /sbin/route
* /bin/netstat
* /etc/network || /etc/sysconfig/network/
* /sbin/ifup
* /sbin/ifdown
* system log files such as /var/log/syslog && /var/log/messages
* /bin/ping
* /etc/resolv.conf
* /etc/hosts
* /etc/hosts.allow && /etc/hosts.deny
* /etc/hostname || /etc/HOSTNAME
* /etc/hostname
* /etc/domainname
* /usr/sbin/traceroute
* /usr/bin/nslookup
* /usr/bin/dig
* /bin/dmesg
[3.34.11]
Objective: Be able to identify common local system and user environment configuration
issues and common repair techniques.
This includes:
* /etc/inittab
* /sbin/init
* /etc/passwd
* /etc/shadow
* /etc/group
* /etc/profile
* /etc/rc.local || /etc/rc.boot
* /usr/sbin/cron
* /usr/bin/crontab
* /var/spool/cron/crontabs/
* /etc/`shell_name`.conf
* /etc/login.defs
* /etc/syslog.conf
1.2.4 hi,L1 Check for important processes using 'ps waux | grep <process>'
1.2.15 L1 Scan /var/spool/mail with 'find /var/spool/mail -size +1000k' to see
if users have uncommonly big mail files
1.2.17 L1 Look at the /proc/filesystems file to see what file systems the kernel
supports
1.3.4 lo,L1 Checking for corrupted files with 'find / -size +1000000k'
3.16.4 Set up a monitoring server to look for downed servers
3.16.6 Configure mon/Big Brother to send alerts through various means
(pagers, E-mail, etc.).
3.16.8 Use lsof to determine if a particular server port is in use.
3.16.10 lo Configure mon/Big Brother to monitor multiple services on multiple
Servers, including ping tests as well as HTTP, SMTP, POP3, IMAP, etc. service
monitoring.
5.1.4 lo,L1 Use snmp to check load usage
5.1.9 lo Setup idled to logoff users that have been sitting idle for too long
6.2.4 L1 Run cmp or diff on known file that do not change like /lib /sbin /boot
/bin /usr/bin /usr/sbin /usr/lib note any changes.
6.2.5 Use 'md5sum' to verify files.
