Les Bell has taken more time to develope the preliminary Network Client
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/
--
Network Client Objectives
[3.13.1, 3.13.2, 3.13.3, 3.13.4, 3.13.5, 3.13.6]
Objective: Configure a LAN to use DHCP allocation of IP addresses
The candidate should be able to: Configure a DHCP server and set default
options. Create a subnet and set options for it. Create a
dynamically-allocated range and set options for it. Add a static host and
set options for a single host. Add bootp hosts. Configure a DHCP relay
agent. Reload the DHCP server after making changes.
Includes tools and files such as:
* dhcpd.conf
* dhcpd.leases
[3.11.1, 3.11.2, 3.11.3, 3.11.4, 3.11.5]
Objective: Configure a LAN to use NIS
The candidate should be able to: Configure an NIS server and create NIS
maps for major configuration files. Configure a system as a NIS client.
Configure searching of local files, DNS, NIS, etc. in nsswitch.conf. Set
up an NIS slave server.
Includes tools and files such as:
* nisupdate, ypbind, ypcat, ypmatch, ypserv, ypswitchm
yppasswd, yppoll, yppush, ypwhich, rpcinfo
* nis.conf, nsswitch.conf, ypserv.conf
* Contents of /etc/nis/: netgroup, nicknames, securenets
[3.18.3, 3.18.5, 3.18.6, 3.18.7]
Objective: Configure a LAN to use LDAP for user authentication
The candidate should be able to: Configure an LDAP server. Configure a
directory hierarchy. Add group, hosts, services and other data to the
hierarchy. Import items from LDIF files and add items with a management
tool. Add users to the directory and change their passwords.
Includes tools and files such as:
* slapd
* slapd.conf
[6.3.7, 3.11.4]
Objective: Configure logon authentication for network services using PAM
The candidate should be able to: Configure PAM to support authentication
via traditional /etc/passwd, shadow passwords, NIS or LDAP.
Includes tools and files such as:
* /etc/pam.d
3.4.3 hi Set up Network address translation to help protect the network from
the Internet.
3.11.1 Set up a NIS password server
3.11.2 Configure an NIS master server by editing the proper files and running
ypinit.
3.11.3 Configure a system to use NIS for its networked system database.
3.11.4 Edit /etc/nsswitch.conf to implement different networked system
databases, such as LDAP or NIS; ensure that the PAM configuration is consistent with
the NSS configuration where necessary.
3.11.5 L1 Set up an NIS slave server
3.13.1 Add static hosts to dhcpd.conf
3.13.2 Configure DHCP options, both as defaults and per subnet, dynamic
range, and static host.
3.13.2 Add dynamic IP ranges to dhcpd.conf, restarting dhcpd afterwards.
3.13.4 Configure dhcpd to serve DHCP requests on the local LAN
3.13.5 Configure a DHCP relay to forward DHCP requests on a local LAN to a
remote DHCP server.
3.13.6 Add bootp hosts in dhcpd.conf
3.18.3 lo Add items to an LDAP hierarchy with LDIF files or with a management
tool.
3.18.5 L1 Add users properly to the LDAP server, including changing user
passwords.
3.18.6 lo Add proper group, hosts, services, etc. information to an LDAP server
suitable for allowing it to act as a networked system database.
3.18.7 lo,L1 Query an LDAP server with ldapsearch for an entry's information.
6.3.7 Configure PAM to specify authentication methods.
