LPI Wiki - User contributions [en]

Volunteer Opportunities

2025-09-10T17:27:00Z

StarnixAdmin:

__FORCETOC__
==Introduction==

Here are a list of ways that you can help LPI.

==Translations==

===Exam Translation===

For this task, we rely on LPI affiliates. If you are interested in helping, please contact one of them (link to affiliates required) to help.

Also, if you are going to help, please get your certification first ;)

If you get this far, please read the [[Translation Instructions]].

===Objective Translation===

The objectives listed on the LPI wiki (see the side bar) could definitely use more volunteers. contact [[User:GMatthewRice]] if you need assistance.

Also, check out [[Translation Instructions#How to use Omega with Wiki Materials|these instructions]].

==Item Writing==

Not much to it: [[VolunteerItemWriting|Volunteer Item Writing]]

==Item Evaluation==

This is the Angoff Studies that are mentioned on the [http://www2.lpi.org/eng/certification/exam_development_process/exam_creation__1 web site].

The [[CutScoreInstructions|instructions are here]].

==Objective Creation and Maintenance==

Please join the [http://list.lpi.org/mailman/listinfo/lpi-examdev LPI Examdev mailing list] for this.

Also, read the [[ObjectiveMaintenanceSchedule| maintenance schedule]].

==Town Halls==

Join us in our [[TownHall]] meetings and voice your opinion on LPI activities and goals.

==Teacher Resources==

Find some useful [[TeacherResources]] here.

==Tools Development==

More information on the [[Xamnet]] project is here.

==Other Things==

[[RozStuff]]

Main Page

2025-09-10T16:51:30Z

StarnixAdmin:

=== Welcome to the Linux Professional Institute wiki! ===

 

This a place for the community to openly discuss everything from exam development topics to LPI policies and procedures.

 

We encourage you to participate in the exam development process by providing your input on our exam objectives. To do so, simply [http://wiki.lpi.org/pubwiki/index.php?title=Special:UserLogin&returnto=Main_Page Create an Account], and then jump in using the navigation bar on the left.

 

You may find the following links useful:

* [http://www.lpi.org/our-certifications/summary-of-certifications The Current Published Exam Objectives]
* [http://www.lpi.org/value-of-certification/our-certification-development-standards The Exam Development Process]
* [http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev LPI Exam Development Mailing List]
* [http://www.lpi.org/about-lpi/frequently-asked-questions LPI's FAQ]
* [http://www.lpi.org/policies LPI's Policies]
* [http://www.mediawiki.org/wiki/Help:Formatting MediaWiki Markup]
* [https://wiki.lpi.org/wiki/Exam_Overview Exam Overview]
* [[Volunteer Opportunities]]

 

Please contact the [mailto:wiki@lpi.org administrator] with any questions or comments about the wiki, or [mailto:info@lpi.org info@lpi.org] for any inquiries regarding exam development.

MediaWiki:Sidebar

2022-03-25T15:49:31Z

StarnixAdmin:

* Exam Objectives
** LinuxEssentials_Objectives_V1.6|Linux Essentials v1.6
** Web_Development_Essentials_Objectives_V1.0|Web Development Essentials v1.0
** LPIC-1_Objectives_V5.0|LPIC-1 v5.0
** LPIC-2|LPIC-2 v4.5
** LPIC-3_300_Objectives|300 Objectives v1.0
** LPIC-300_Objectives_V3.0|300 Objectives v3.0
** LPIC-3_303_Objectives|303 Objectives v2.0
** LPIC-303_Objectives_V3.0|303 Objectives v3.0
** LPIC-3_304_Objectives|304 Objectives v2.0
** LPIC-305_Objectives_V3.0|305 Objectives v3.0
** LPIC-306_Objectives_V3.0|306 Objectives v3.0
** DevOps_Tools_Engineer_Objectives|DevOps Tools Engineer Objectives v1.0
** BSD_Specialist_Objectives_V1.0|BSD Specialist Objectives v1.0

* SEARCH

* navigation
** mainpage|mainpage-description
** recentchanges-url|recentchanges
** http://www.lpi.org|LPI Website

* TOOLBOX

Main Page

2020-02-18T16:42:44Z

StarnixAdmin:

__NOTITLE__
=== Welcome to the Linux Professional Institute wiki! ===

 

This a place for the community to openly discuss everything from exam development topics to LPI policies and procedures.

 

We encourage you to participate in the exam development process by providing your input on our exam objectives. To do so, simply [http://wiki.lpi.org/pubwiki/index.php?title=Special:UserLogin&returnto=Main_Page Create an Account], and then jump in using the navigation bar on the left.

 

You may find the following links useful:

* [http://www.lpi.org/our-certifications/summary-of-certifications The Current Published Exam Objectives]
* [http://www.lpi.org/value-of-certification/our-certification-development-standards The Exam Development Process]
* [http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev LPI Exam Development Mailing List]
* [http://www.lpi.org/about-lpi/frequently-asked-questions LPI's FAQ]
* [http://www.lpi.org/policies LPI's Policies]
* [http://www.mediawiki.org/wiki/Help:Formatting MediaWiki Markup]
* [https://wiki.lpi.org/wiki/Exam_Overview Exam Overview]
* [[Volunteer Opportunities]]

 

Please contact the [mailto:wiki@lpi.org administrator] with any questions or comments about the wiki, or [mailto:info@lpi.org info@lpi.org] for any inquiries regarding exam development.

Main Page

2019-07-09T01:15:49Z

StarnixAdmin:

__NOTITLE__
=== Welcome to the Linux Professional Institute wiki! ===

 

This a place for the community to openly discuss everything from exam development topics to LPI policies and procedures.

 

We encourage you to participate in the exam development process by providing your input on our exam objectives. To do so, simply [http://wiki.lpi.org/pubwiki/index.php?title=Special:UserLogin&returnto=Main_Page Create an Account], and then jump in using the navigation bar on the left.

 
We have information on:
* [[Free Training Materials]]

 

You may find the following links useful:

* [http://www.lpi.org/our-certifications/summary-of-certifications The Current Published Exam Objectives]
* [http://www.lpi.org/value-of-certification/our-certification-development-standards The Exam Development Process]
* [http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev LPI Exam Development Mailing List]
* [http://www.lpi.org/about-lpi/frequently-asked-questions LPI's FAQ]
* [http://www.lpi.org/policies LPI's Policies]
* [http://www.mediawiki.org/wiki/Help:Formatting MediaWiki Markup]
* [https://wiki.lpi.org/wiki/Exam_Overview Exam Overview]
* [[Volunteer Opportunities]]

 

Please contact the [mailto:wiki@lpi.org administrator] with any questions or comments about the wiki, or [mailto:info@lpi.org info@lpi.org] for any inquiries regarding exam development.

LinuxEssentials Objectives V1.5

2017-12-12T18:40:31Z

StarnixAdmin: Reverted edits by Lala12 (talk) to last revision by CesarBrod

__FORCETOC__
==Introduction and Exam Development Workshops==

The description of the entire Linux Essentials Programme programme is listed [[LinuxEssentialsProgramme|here]].

The purpose of the Linux Essentials Certificate is to define the basic knowledge required to competently use a desktop or mobile device using a Linux Operating System. The associated Linux Essentials Program will guide and encourage youth (and those new to Linux and Open Source) to understand the place of Linux and Open Source in the context of the broader IT industry.

==FAQ==

Questions and answers on the Linux Essentials Program and Exam are listed [[LinuxEssentials/FAQs|here]].

==Minimally Qualified Candidate Description==

This is a description of a candidate that is just barely
qualified to pass the LPI Linux Essentials exam. This hypothetical
person is called the Minimally Qualified Candidate (MQC). Standards on
the Linux Essentials exam should be set so that this person (and
anyone more able) would pass but anyone less able would not pass.

The successful candidate should have an understanding of the Linux and Open Source industry and knowledge of the most popular Open Source Applications. The candidate should understand the major components of the Linux operating system, and have the technical proficiency to work on the Linux command line. The MQC has a basic understanding of security and administration related topics such
as user/group management, working on the command line and permissions. The Linux Essentials Certificate holder is most likely the end user of a mostly managed system.

The '''LPI Linux Essentials Certificate Holder MQC''' typically:

* Has a basic understanding of FOSS, the various communities and licenses.
* Understands the basic concepts of processes, programs and the components of an Operating System.
* Has a basic knowledge of computer hardware.
* Has a basic appreciation of system security, users/groups and file permissions for public and private directories.
* Basic understanding of how to make the system accessible and able to connect to other computers on a Local Area Network (LAN).
* Demonstrates a knowledge of Open Source Applications in the Workplace as they relate to Closed Source equivalents.
* Understands navigation systems on a Linux Desktop and where to go for help.
* Has a rudimentary ability to work on the command line and with files.
* Make and restore simple backups and archives.
* Can use a basic command line editor.
* Understands file compression.
* Ability to create and run simple scripts.

==Version Information==

These objectives are version 1.5.

This is also a [[LESummaryVersion1To1.5|summary and detailed information]] on the changes from version 1.0 to 1.5 of the objectives.

The [[LinuxEssentials Objectives V1|version 1.0 objectives]] can be found [[LinuxEssentials Objectives V1|here]].

==Addenda==

There are currently no addenda.

==Translations of Objectives==

The following translations of the objectives are available on this wiki:

* [[LinuxEssentials Objectives V1.5|English]].
* [[LinuxEssentials Objectives V1.5(AR)|Arabic]].
* [[LinuxEssentials Objectives V1.5(PT-BR)|Brazilian Portuguese]].
* [[LinuxEssentials Objectives V1.5(FR)|French]].
* [[LinuxEssentials Objectives V1.5(DE)|German]].
* [[LinuxEssentials Objectives V1.5(EL)|Greek]].
* [[LinuxEssentials Objectives V1.5(ES)|Spanish]].
* [[LinuxEssentials Objectives V1.5(TR)|Turkish]].
* [[LinuxEssentials Objectives V1.5(IT)|Italian]].
* [[LinuxEssentials Objectives V1.5(NL)|Dutch]].

==Objectives==

===''Topic 1: The Linux Community and a Career in Open Source (weight: 7)''===

====1.1 Linux Evolution and Popular Operating Systems====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Knowledge of Linux development and major distributions.

|}

'''Key Knowledge Areas:'''

* Open Source Philosophy
* Distributions
* Embedded Systems

'''The following is a partial list of the used files, terms and utilities:'''

* Android
* Debian, Ubuntu (LTS)
* CentOS, openSUSE, Red Hat
* Linux Mint, Scientific Linux

====1.2 Major Open Source Applications====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Awareness of major applications as well as their uses and development.

|}

'''Key Knowledge Areas:'''

* Desktop Applications
* Server Applications
* Development Languages
* Package Management Tools and repositories

'''The following is a partial list of the used files, terms and utilities:'''

* OpenOffice.org, LibreOffice, Thunderbird, Firefox, GIMP
* Apache HTTPD, NGINX, MySQL, NFS, Samba
* C, Java, Perl, shell, Python, PHP
* dpkg, apt-get, rpm, yum

====1.3 Understanding Open Source Software and Licensing====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Open communities and licensing Open Source Software for business.

|}

'''Key Knowledge Areas:'''

* Licensing
* Free Software Foundation (FSF), Open Source Initiative (OSI)

'''The following is a partial list of the used files, terms and utilities:'''

* GPL, BSD, Creative Commons
* Free Software, Open Source Software, FOSS, FLOSS
* Open Source business models

====1.4 ICT Skills and Working in Linux====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Basic Information and Communication Technology (ICT) skills and working in Linux.

|}

'''Key Knowledge Areas:'''

* Desktop Skills
* Getting to the Command Line
* Industry uses of Linux, Cloud Computing and Virtualization

'''The following is a partial list of the used files, terms and utilities:'''

* Using a browser, privacy concerns, configuration options, searching the web and saving content
* Terminal and Console
* Password issues
* Privacy issues and tools
* Use of common open source applications in presentations and projects

===''Topic 2: Finding Your Way on a Linux System (weight: 9)''===

====2.1 Command Line Basics====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Basics of using the Linux command line.

|}

'''Key Knowledge Areas:'''

* Basic shell
* Command line syntax
* Variables
* Globbing
* Quoting

'''The following is a partial list of the used files, terms and utilities:'''

* Bash
* echo
* history
* PATH env variable
* export
* type

====2.2 Using the Command Line to Get Help ====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Running help commands and navigation of the various help systems.

|}

'''Key Knowledge Areas:'''

* Man
* Info

'''The following is a partial list of the used files, terms and utilities:'''

* man
* info
* Man pages
* /usr/share/doc/
* locate

====2.3 Using Directories and Listing Files====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Navigation of home and system directories and listing files in various locations.

|}

'''Key Knowledge Areas:'''

* Files, directories
* Hidden files and directories
* Home
* Absolute and relative paths

'''The following is a partial list of the used files, terms and utilities:'''

* Common options for ls
* Recursive listings
* cd
* '''.''' and '''..'''
* home and ~

====2.4 Creating, Moving and Deleting Files====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Create, move and delete files and directories under the home directory.

|}

'''Key Knowledge Areas:'''

* Files and directories
* Case sensitivity
* Simple globbing and quoting

'''The following is a partial list of the used files, terms and utilities:'''

* mv, cp, rm, touch
* mkdir, rmdir

===''Topic 3: The Power of the Command Line (weight: 9)''===

====3.1 Archiving Files on the Command Line====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Archiving files in the user home directory.

|}

'''Key Knowledge Areas:'''

* Files, directories
* Archives, compression

'''The following is a partial list of the used files, terms and utilities:'''

* tar
* Common tar options
* gzip, bzip2
* zip, unzip

====3.2 Searching and Extracting Data from Files====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Search and extract data from files in the home directory.

|}

'''Key Knowledge Areas:'''

* Command line pipes
* I/O re-direction
* Basic Regular Expressions using ., [ ], *, and ?

'''The following is a partial list of the used files, terms and utilities:'''

* grep
* less
* cat, head, tail
* sort
* cut
* wc

====3.3 Turning Commands into a Script====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Turning repetitive commands into simple scripts.

|}

'''Key Knowledge Areas:'''

* Basic shell scripting
* Awareness of common text editors

'''The following is a partial list of the used files, terms and utilities:'''

* #! (shebang)
* /bin/bash
* Variables
* Arguments
* for loops
* echo
* Exit status

===''Topic 4: The Linux Operating System (weight: 8)''===

====4.1 Choosing an Operating System====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Knowledge of major operating systems and Linux distributions.

|}

'''Key Knowledge Areas:'''

* Windows, Mac, Linux differences
* Distribution life cycle management

'''The following is a partial list of the used files, terms and utilities:'''

* GUI versus command line, desktop configuration
* Maintenance cycles, Beta and Stable

====4.2 Understanding Computer Hardware====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Familiarity with the components that go into building desktop and server computers.

|}

'''Key Knowledge Areas:'''

* Hardware

'''The following is a partial list of the used files, terms and utilities:'''

* Motherboards, processors, power supplies, optical drives, peripherals
* Hard drives and partitions, /dev/sd*
* Drivers

====4.3 Where Data is Stored====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Where various types of information are stored on a Linux system.

|}

'''Key Knowledge Areas:'''

* Programs and configuration, packages and package databases
* Processes, memory addresses, system messaging and logging

'''The following is a partial list of the used files, terms and utilities:'''

* ps, top, free
* syslog, dmesg
* /etc/, /var/log/
* /boot/, /proc/, /dev/, /sys/

====4.4 Your Computer on the Network====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Querying vital networking configuration and determining the basic requirements for a computer on a Local Area Network (LAN).

|}

'''Key Knowledge Areas:'''

* Internet, network, routers
* Querying DNS client configuration
* Querying Network configuration

'''The following is a partial list of the used files, terms and utilities:'''

* route, ip route show
* ifconfig, ip addr show
* netstat, ip route show
* /etc/resolv.conf, /etc/hosts
* IPv4, IPv6
* ping
* host

===''Topic 5: Security and File Permissions (weight: 7)''===

====5.1 Basic Security and Identifying User Types====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Various types of users on a Linux system.

|}

'''Key Knowledge Areas:'''

* Root and Standard Users
* System users

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/passwd, /etc/group
* id, who, w
* sudo, su

====5.2 Creating Users and Groups====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Creating users and groups on a Linux system.

|}

'''Key Knowledge Areas:'''

* User and group commands
* User IDs

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/passwd, /etc/shadow, /etc/group, /etc/skel/
* id, last
* useradd, groupadd
* passwd

====5.3 Managing File Permissions and Ownership====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Understanding and manipulating file permissions and ownership settings.

|}

'''Key Knowledge Areas:'''

* File/directory permissions and owners

'''The following is a partial list of the used files, terms and utilities:'''

* ls -l, ls -a
* chmod, chown

====5.4 Special Directories and Files====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Special directories and files on a Linux system including special permissions.

|}

'''Key Knowledge Areas:'''

* Using temporary files and directories
* Symbolic links

'''The following is a partial list of the used files, terms and utilities:'''

* /tmp/, /var/tmp/ and Sticky Bit
* ls -d
* ln -s

===''Reference Material''===

===Notes and Comments===

Feel free to add comments below:

MediaWiki:Sidebar

2017-03-08T19:05:03Z

StarnixAdmin:

MediaWiki:Sidebar

2017-03-08T19:04:44Z

StarnixAdmin:

Main Page

2016-11-24T22:43:20Z

StarnixAdmin:

__NOTITLE__
=== Welcome to the Linux Professional Institute wiki! ===

 

This a place for the community to openly discuss everything from exam development topics to LPI policies and procedures.

 

We encourage you to participate in the exam development process by providing your input on our exam objectives. To do so, simply [http://wiki.lpi.org/pubwiki/index.php?title=Special:UserLogin&returnto=Main_Page Create an Account], and then jump in using the navigation bar on the left.

 
We have information on:
* [[Free Training Materials]]

 

You may find the following links useful:

* [http://www.lpi.org/our-certifications/summary-of-certifications The Current Published Exam Objectives]
* [http://www.lpi.org/value-of-certification/our-certification-development-standards The Exam Development Process]
* [http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev LPI Exam Development Mailing List]
* [http://www.lpi.org/about-lpi/frequently-asked-questions LPI's FAQ]
* [http://www.lpi.org/policies LPI's Policies]
* [http://www.mediawiki.org/wiki/Help:Formatting MediaWiki Markup]
* [[Volunteer Opportunities]]

 

Please contact the [mailto:wiki@lpi.org administrator] with any questions or comments about the wiki, or [mailto:info@lpi.org info@lpi.org] for any inquiries regarding exam development.

LPIC-3 303 Objectives

2016-05-24T14:24:23Z

StarnixAdmin: Redirected page to LPIC-303 Objectives V2

#REDIRECT [[LPIC-303 Objectives V2]]

Main Page

2016-04-05T18:34:21Z

StarnixAdmin:

__NOTITLE__
=== Welcome to the Linux Professional Institute wiki! ===

 

This a place for the community to openly discuss everything from exam development topics to LPI policies and procedures.

 

We encourage you to participate in the exam development process by providing your input on our exam objectives. To do so, simply [http://wiki.lpi.org/pubwiki/index.php?title=Special:UserLogin&returnto=Main_Page Create an Account], and then jump in using the navigation bar on the left.

 
We have information on:
* [[Free Training Materials]]

 

You may find the following links useful:

* [http://www.lpi.org/eng/certification/the_lpic_program The Current Published Exam Objectives]
* [http://www.lpi.org/linux-certifications/structure/exam-creation The Exam Development Process]
* [http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev LPI Exam Development Mailing List]
* [https://www.lpi.org/about-lpi/frequently-asked-questions LPI's FAQ]
* [https://www.lpi.org/about-lpi/policies LPI's Policies]
* [http://www.mediawiki.org/wiki/Help:Formatting MediaWiki Markup]
* [[Volunteer Opportunities]]

 

Please contact the [mailto:wiki@lpi.org administrator] with any questions or comments about the wiki, or [mailto:info@lpi.org info@lpi.org] for any inquiries regarding exam development.

Main Page

2016-04-05T18:34:04Z

StarnixAdmin:

__NOTITLE__
=== Welcome to the Linux Professional Institute wiki! ===

 

This a place for the community to openly discuss everything from exam development topics to LPI policies and procedures.

 

We encourage you to participate in the exam development process by providing your input on our exam objectives. To do so, simply [http://wiki.lpi.org/pubwiki/index.php?title=Special:UserLogin&returnto=Main_Page Create an Account], and then jump in using the navigation bar on the left.

 
We have information on:
* [[Free Training Materials]]

 

You may find the following links useful:

* [http://www.lpi.org/eng/certification/the_lpic_program The Current Published Exam Objectives]
* [http://www.lpi.org/linux-certifications/structure/exam-creation The Exam Development Process]
* [http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev LPI Exam Development Mailing List]
* [https://www.lpi.org/about-lpi/frequently-asked-questions LPI's FAQ]
* [https://www.lpi.org/about-lpi/policies LPI's policies]
* [http://www.mediawiki.org/wiki/Help:Formatting MediaWiki Markup]
* [[Volunteer Opportunities]]

 

Please contact the [mailto:wiki@lpi.org administrator] with any questions or comments about the wiki, or [mailto:info@lpi.org info@lpi.org] for any inquiries regarding exam development.

Main Page

2016-04-05T17:40:44Z

StarnixAdmin:

__NOTITLE__
=== Welcome to the Linux Professional Institute wiki! ===

 

This a place for the community to openly discuss everything from exam development topics to LPI policies and procedures.

 

We encourage you to participate in the exam development process by providing your input on our exam objectives. To do so, simply [http://wiki.lpi.org/pubwiki/index.php?title=Special:UserLogin&returnto=Main_Page Create an Account], and then jump in using the navigation bar on the left.

 
We have information on:
* [[Free Training Materials]]

 

You may find the following links useful:

* [http://www.lpi.org/eng/certification/the_lpic_program The Current Published Exam Objectives]
* [http://www.lpi.org/linux-certifications/structure/exam-creation The Exam Development Process]
* [http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev LPI Exam Development Mailing List]
* [http://www.lpi.org/linux-certifications/faq LPI's FAQ]
* [http://www.mediawiki.org/wiki/Help:Formatting MediaWiki Markup]
* [[Volunteer Opportunities]]

 

Please contact the [mailto:wiki@lpi.org administrator] with any questions or comments about the wiki, or [mailto:info@lpi.org info@lpi.org] for any inquiries regarding exam development.

LPIC-305

2016-03-04T16:05:47Z

StarnixAdmin:

__FORCETOC__
==Notice==

Currently, this exam is not in development.

==Introduction==
The description of the entire [[LPIC-3]] programme is listed [[LPIC-3|here]].

LPI is just getting underway in the development of the next LPIC-3 Enterprise exam. This exam will cover Mail and Messaging Services.

The main milestones to be achieved are:

# Consult with industry, partners and communities on requirements
# Create draft objectives
# Perform a JTA (Job Task Analysis) survey to determine objective weighting
# Develop exam content (aka exam items)
# Have a 305 Beta exam period for public feedback and testing
# Evaluation JTA and Beta exam results
# Launch final 305 exam

We are commencing this milestone 1 as described above and would like to have the final exam launch in 2011.
 

==How To Add to This Discussion==

Please add to the discussion on the lpi-examdev mailing list:

   http://list.lpi.org/mailman/listinfo/lpi-examdev

This page will be updated as we progress. Alternatively, register on this wiki and add your comments below.

==Want to Be a Subject Matter Expert for this exam???==

Please contact G. Matthew Rice [[mailto:mrice@lpi.org]] or speak up on the mailing list.

 

==Topics to Be Considered for Coverage==

This is a brief (not exclusive nor inclusive) list of topics under consideration:

Mail Services

* E-mail Concepts and Troubleshooting
* MTA (Postfix and/or Sendmail and/or Exim)
* IMAP/POP services (courier and/or dovecot and/or uw-imap)
* Virus scanning (Amavis)
* Spam filtering (SpamAssasin)
* MUA (Mail User Agents aka e-mail clients)
* Secure POP, IMAP, SMTP (setting up certificates, configuration)
* Integration with LDAP and/or MySQL
* greylisting
* blacklisting and RBLs

Messaging Services

* Messaging Servers (OpenFire and/or Jabberd)
* Messaging clients (Pidgin, Kopete)
* Messaging protocols (XMPP)
* Integration with LDAP and/or MySQL
* IRC clients and servers (maybe)

==The Minimally Qualified Candidate for This Exam==

This is a description of a Linux professional that is just barely
qualified to pass the LPI Level 3 Linux exams. This hypothetical person
is called the Minimally Qualified Candidate (MQC). Standards on the
Level 3 exams should be set so that this person (and anyone more able)
would pass but anyone less able would not pass.

An LPI certified Level 3 Linux professional (designated LPIC-3) should
have the technical capability to perform system administration at the
enterprise level. A [[LPIC-3]] certification holder should be able to understand, plan roll-outs,
install, configure, maintain and troubleshoot the technologies being
tested. These technologies differ for each exam but the level of ability
is at an enterprise level.

The LPIC-3 MQC typically (Yes, some of these bullets are specific to particular exams in the LPIC-3 series):

* Has installed and maintained Linux on a number of computers for various purposes for a number of years.
* Has integration experience with diverse technologies and operating systems.
* Has professional experience as, or training for, an enterprise level Linux professional. (Including having experience as a part of another role.)
* Is comfortable with advanced and enterprise levels of Linux administration including installation, management, security, troubleshooting and maintenance.
* Is able to use opensource tools to measure capacity planning and troubleshooting resource problems.
* Is able create scripts in Bash or Perl or has knowledge of at least one system programming language (such as C).
* Is able to plan, architecture, design, build and implement a full environment using E-mail and Messaging services as well as measure the capacity planning and security of the services.

==Community Comments==

Please add your comments or see above to join lpi-examdev mailing list.

Main Page

2014-10-16T20:25:41Z

StarnixAdmin:

__NOTITLE__
=== Welcome to the Linux Professional Institute wiki! ===

 

This a place for the community to openly discuss everything from exam development topics to LPI policies and procedures.

 

We encourage you to participate in the exam development process by providing your input on our exam objectives. To do so, simply [http://wiki.lpi.org/pubwiki/index.php?title=Special:UserLogin&returnto=Main_Page Create an Account], and then jump in using the navigation bar on the left.

 
We have information on:
* Body of Knowledge Projects
** [[LPIC-2_BoK|LPIC-2 Body of Knowledge]]
* [[LPIC-3|LPIC-3 Certification]]
* [[LPIC-3_305_Objectives|News on the upcoming 305 exam]]

 

You may find the following links useful:

* [http://www.lpi.org/eng/certification/the_lpic_program The Current Published Exam Objectives]
* [http://www.lpi.org/linux-certifications/structure/exam-creation The Exam Development Process]
* [http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev LPI Exam Development Mailing List]
* [http://www.lpi.org/linux-certifications/faq LPI's FAQ]
* [http://www.mediawiki.org/wiki/Help:Formatting MediaWiki Markup]
* [[Volunteer Opportunities]]

 

Please contact the [mailto:wiki@lpi.org administrator] with any questions or comments about the wiki, or [mailto:info@lpi.org info@lpi.org] for any inquiries regarding exam development.

MediaWiki:Sidebar

2014-01-17T18:59:39Z

StarnixAdmin:

MediaWiki:Sidebar

2014-01-17T18:59:25Z

StarnixAdmin:

MediaWiki:Sidebar

2014-01-17T18:58:56Z

StarnixAdmin:

Main Page

2013-08-08T15:19:35Z

StarnixAdmin:

__NOTITLE__
=== Welcome to the Linux Professional Institute wiki! ===

 

This a place for the community to openly discuss everything from exam development topics to LPI policies and procedures.

 

We encourage you to participate in the exam development process by providing your input on our exam objectives. To do so, simply [http://wiki.lpi.org/pubwiki/index.php?title=Special:UserLogin&returnto=Main_Page Create an Account], and then jump in using the navigation bar on the left.

 
We have information on:
* Body of Knowledge Projects
** [[LPIC-2_BoK|LPIC-2 Body of Knowledge]]
* [[LPIC-3|LPIC-3 Certification]]
* [[LPIC-3_305_Objectives|News on the upcoming 305 exam]]

 

You may find the following links useful:

* [http://www.lpi.org/eng/certification/the_lpic_program The Current Published Exam Objectives]
* [http://www.lpi.org/eng/certification/exam_development_process The Exam Development Process]
* [http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev LPI Exam Development Mailing List]
* [http://www.lpi.org/linux-certifications/faq LPI's FAQ]
* [http://www.mediawiki.org/wiki/Help:Formatting MediaWiki Markup]
* [[Volunteer Opportunities]]

 

Please contact the [mailto:wiki@lpi.org administrator] with any questions or comments about the wiki, or [mailto:info@lpi.org info@lpi.org] for any inquiries regarding exam development.

LPIC2SummaryVersion3To4

2013-06-12T13:40:40Z

StarnixAdmin:

201.2 renamed to Compiling and patching a Linux kernel

201.3 merged with 201.2

201.4 merged with 201.2

201.5 renamed to Kernel runtime manangement and troubleshooting (renumbered to 201.3)

202.1 renamed to Customising SysV-init system startup

202.2 added awareness of UEFI

202.3 added 'Alternate boot loaders'

203.2 changed content

NB: dropped badblocks, added smartd/smartctl
dropped ReiserFS, added Btrfs

203.4 merged with 201.5

204.2 new content

NB: added iSCSI

205.2 renamed to Advanced Network Configuration

NB: moved OpenVPN to 212.6 (new objective)

205.3 added content

NB: added TCP wrapper files /etc/hosts.*

205.4 moved/renumbered to 206.3

207 entire objective moved to 202 exam

208.1 renamed to Basic Apache Configuration

208.2 renamed to Apache configuration for HTTPS

NB: virtual hosts and file access moved to 208.1

208.3 renamed from "Implementing a Proxy Server" to "Implementing a Caching Proxy with Squid"

NB: Updated to Squid version 3.x

208.4 created "Implementing Nginx as a web server and reverse proxy

NB: covers basics of Nginx

210.4 created "LDAP Server Basics"

211.1 changed focus from Sendmail to Postfix

212.2 changed to 'Managing FTP servers' from 'Securing FTP servers'

212.3 dropped much of the client side of SSH (it's covered in LPIC-1)

212.4 dropped TCP Wrappers (it's covered in LPIC-1)

212.5 renumbered to 212.4

212.6 renumbered to 212.5

213.1 merged into 202.2

NB: init.d dropped/redundant with 213.3

213.2 merged into 201.5

NB: strings moved to 201.4
ltrace to be merged with 102.3
strace to be merged with 102.3

dropped as redundant
* Various system and daemon log files
* Kernel syslog entries in system logs (if entry is able to be gained)

213.3 dropped/redundant with LPIC-1

213.4 dropped/redundant with LPIC-1

NB: syctl, /etc/sysctl.conf, /etc/sysctl.d/ moved to 201.5

306 (entire Topic) was merged into LPIC-2 201 exam (renumbered to 200)

306.2 merged with 306.2; numbered 200.1

306.3 dropped.

306.4 added collectd and awareness of other monitoring solutions. renumbered to 200.2

LPIC2SummaryVersion3To4

2013-06-12T13:40:16Z

StarnixAdmin:

201.2 renamed to Compiling and patching a Linux kernel

201.3 merged with 201.2

201.4 merged with 201.2

201.5 renamed to Kernel runtime manangement and troubleshooting (renumbered to 201.3)

202.1 renamed to Customising SysV-init system startup

202.2 added awareness of UEFI

202.3 added 'Alternate boot loaders'

203.2 changed content

NB: dropped badblocks, added smartd/smartctl
dropped ReiserFS, added Btrfs

203.4 merged with 201.5

204.2 new content

NB: added Fibre Channel and iSCSI

205.2 renamed to Advanced Network Configuration

NB: moved OpenVPN to 212.6 (new objective)

205.3 added content

NB: added TCP wrapper files /etc/hosts.*

205.4 moved/renumbered to 206.3

207 entire objective moved to 202 exam

208.1 renamed to Basic Apache Configuration

208.2 renamed to Apache configuration for HTTPS

NB: virtual hosts and file access moved to 208.1

208.3 renamed from "Implementing a Proxy Server" to "Implementing a Caching Proxy with Squid"

NB: Updated to Squid version 3.x

208.4 created "Implementing Nginx as a web server and reverse proxy

NB: covers basics of Nginx

210.4 created "LDAP Server Basics"

211.1 changed focus from Sendmail to Postfix

212.2 changed to 'Managing FTP servers' from 'Securing FTP servers'

212.3 dropped much of the client side of SSH (it's covered in LPIC-1)

212.4 dropped TCP Wrappers (it's covered in LPIC-1)

212.5 renumbered to 212.4

212.6 renumbered to 212.5

213.1 merged into 202.2

NB: init.d dropped/redundant with 213.3

213.2 merged into 201.5

NB: strings moved to 201.4
ltrace to be merged with 102.3
strace to be merged with 102.3

dropped as redundant
* Various system and daemon log files
* Kernel syslog entries in system logs (if entry is able to be gained)

213.3 dropped/redundant with LPIC-1

213.4 dropped/redundant with LPIC-1

NB: syctl, /etc/sysctl.conf, /etc/sysctl.d/ moved to 201.5

306 (entire Topic) was merged into LPIC-2 201 exam (renumbered to 200)

306.2 merged with 306.2; numbered 200.1

306.3 dropped.

306.4 added collectd and awareness of other monitoring solutions. renumbered to 200.2

LPIC-2 Objectives V4

2013-06-12T13:03:58Z

StarnixAdmin: /* 201.1 Kernel components (weight: 2) */

__FORCETOC__
==Overview of Tasks==

This is a required exam for LPI certification Level 2. It covers advanced skills for the Linux professional that are common across all distributions of Linux.

To pass LPIC-2, the candidate should be able to:

* Administer a small to medium-sized site
* Plan, implement, maintain, keep consistent, secure, and troubleshoot a small mixed (MS, Linux) network, including a:
** LAN server (Samba, NFS, DNS, DHCP, client management)
** Internet Gateway (firewall, VPN, SSH, web cache/proxy, mail)
** Internet Server (web server and reverse proxy, FTP server)
* Supervise assistants
* Advise management on automation and purchases

 

==Version Information==

These objectives are version 4.0.0. This version is to go live on Oct 1, 2013.

This is also a [[LPIC2SummaryVersion3To4|summary and detailed information]] on the changes from version 3.5.x to 4.0.0 of the objectives.

The [[LPIC-2_Objectives_V3|version 3.x of the LPIC-2 Objectives]] are still online.
 

==Addenda==

===''Version Update (Oct 1st, 2013)''===

* updated to version 4.0.0

 

==Translations of Objectives==

The following translations of the objectives are available on this wiki:

* [[LPIC-2_Objectives|English]]

* [[LPIC-2_Objectives(ES)|Spanish]]

* [[LPIC-2_Objectives(RU)|Russian]]

* [[LPIC-2_Objectives(Greek)|Greek]]

* [[LPIC-2_Objectives(Turkish)|Turkish]]

* [[LPIC-2_Objectives(FR)|French]]

 

==Objectives: Exam 201==

===''Topic 200: Capacity Planning''===

====200.1 Measure and Troubleshoot Resource Usage (weight: 6)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 6
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Candidates should be able to measure hardware resource and network bandwidth, identify and troubleshoot resource problems.

|}

'''Key Knowledge Areas:'''

* Measure CPU usage.

* Measure memory usage.

* Measure disk I/O.

* Measure network I/O.

* Measure firewalling and routing throughput.

* Map client bandwidth usage.

* Match / correlate system symptoms with likely problems.

* Estimate throughput and identify bottlenecks in a system including networking.

'''The following is a partial list of the used files, terms and utilities:'''

* iostat

* vmstat

* netstat

* pstree, ps

* w

* lsof

* top

* uptime

* sar

* swap

* processes blocked on I/O

* blocks in

* blocks out

 

====200.2 Predict Future Resource Needs (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Candidates should be able to monitor resource usage to predict future resource needs.

|}

'''Key Knowledge Areas:'''

* Use collectd to monitor IT infrastructure usage.

* Predict capacity break point of a configuration.

* Observe growth rate of capacity usage.

* Graph the trend of capacity usage.

* Awareness of monitoring solutions such as Nagios, MRTG and Cacti

'''The following is a partial list of the used files, terms and utilities:'''

* diagnose

* predict growth

* resource exhaustion

 
 

===''Topic 201: Linux Kernel''===

====201.1 Kernel components (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to utilise kernel components that are necessary to specific hardware, hardware drivers, system resources and requirements. This objective includes implementing different types of kernel images, understanding stable and longterm kernels and patches, as well as using kernel modules.
|}

'''Key Knowledge Areas:'''

* Kernel 2.6.x documentation

* Kernel 3.x documentation

'''The following is a partial list of the used files, terms and utilities:'''

* /usr/src/linux

* /usr/src/linux/Documentation

* zImage

* bzImage

 

====201.2 Compiling a Linux kernel (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly configure a kernel to include or disable specific features of the Linux kernel as necessary. This objective includes compiling and recompiling the Linux kernel as needed, updating and noting changes in a new kernel, creating an initrd image and installing new kernels.
|}

'''Key Knowledge Areas:'''

* /usr/src/linux/

* Kernel Makefiles

* Kernel 2.6.x/3.x make targets

* Customize the current kernel configuration.

* Build a new kernel and appropriate kernel modules.

* Install a new kernel and any modules.

* Ensure that the boot manager can locate the new kernel and associated files.

* Module configuration files

* Awareness of dracut

'''The following is a partial list of the used files, terms and utilities:'''

* mkinitrd

* mkinitramfs

* make

* make targets (all, config, xconfig, menuconfig, gconfig, oldconfig, mrproper, zImage, bzImage, modules, modules_install, rpm-pkg, binrpm-pkg, deb-pkg)

* gzip

* bzip2

* module tools

* /usr/src/linux/.config

* /lib/modules/kernel-version/*

* depmod

 

====201.3 Kernel runtime management and troubleshooting (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to manage and/or query a 2.6.x or 3.x kernel and its loadable modules. Candidates should be able to identify and correct common boot and run time issues. Candidates should understand device detection and management using udev. This objective includes troubleshooting udev rules.
|}

'''Key Knowledge Areas:'''

* Use command-line utilities to get information about the currently running kernel and kernel modules.

* Manually load and unload kernel modules.

* Determine when modules can be unloaded.

* Determine what parameters a module accepts.

* Configure the system to load modules by names other than their file name.

* /proc filesystem

* Content of /, /boot , and /lib/modules

* Tools and utilities to analyse information about the available hardware

* udev rules

'''The following is a partial list of the used files, terms and utilities:'''

* /lib/modules/kernel-version/modules.dep

* module configuration files in /etc

* /proc/sys/kernel/

* /sbin/depmod

* /sbin/rmmod

* /sbin/modinfo

* /bin/dmesg

* /sbin/lspci

* /usr/bin/lsdev

* /sbin/lsmod

* /sbin/modprobe

* /sbin/insmod

* /bin/uname

* /usr/bin/lsusb

* /etc/sysctl.conf, /etc/sysctl.d/

* /sbin/sysctl

* udevmonitor

* /etc/udev

 
 

===''Topic 202: System Startup''===

====202.1 Customising SysV-init system startup (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to query and modify the behaviour of system services at various run levels. A thorough understanding of the init structure and boot process is required. This objective includes interacting with run levels.
|}

'''Key Knowledge Areas:'''

* Linux Standard Base Specification (LSB)

* SysV init environment

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/inittab

* /etc/init.d/

* /etc/rc.d/

* chkconfig

* update-rc.d

* init and telinit

 

====202.2 System recovery (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly manipulate a Linux system during both the boot process and during recovery mode. This objective includes using both the init utility and init-related kernel options. Candidates should be able to determine the cause of errors in loading and usage of bootloaders. GRUB version 2 and GRUB Legacy are the bootloaders of interest.
|}

'''Key Knowledge Areas:'''

* GRUB version 2 and Legacy

* grub shell

* boot loader start and hand off to kernel

* kernel loading

* hardware initialisation and setup

* daemon/service initialisation and setup

* Know the different boot loader install locations on a hard disk or removable device

* Overwriting standard boot loader options and using boot loader shells

* Awareness of UEFI

'''The following is a partial list of the used files, terms and utilities:'''

* mount

* fsck

* inittab, telinit and init with SysV init

* The contents of /boot/ and /boot/grub/

* GRUB

* grub-install

* initrd, initramfs

* Master boot record

 

====202.3 Alternate Bootloaders (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be aware of other bootloaders and their major features.
|}

'''Key Knowledge Areas:'''

* LILO

* SYSLINUX, ISOLINUX, PXELINUX

* Understanding of PXE

'''The following is a partial list of the used files, terms and utilities:'''

* lilo, /etc/lilo.conf

* syslinux

* extlinux

* isolinux.bin

* isolinux.cfg

* pxelinux.0

* pxelinux.cfg/*

 
 

===''Topic 203: Filesystem and Devices''===

====203.1 Operating the Linux filesystem (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly configure and navigate the standard Linux filesystem. This objective includes configuring and mounting various filesystem types.
|}

'''Key Knowledge Areas:'''

* The concept of the fstab configuration

* Tools and utilities for handling SWAP partitions and files

* Use of UUIDs for identifying and mounting file systems

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/fstab

* /etc/mtab

* /proc/mounts

* mount and umount

* blkid

* sync

* swapon

* swapoff

 

====203.2 Maintaining a Linux filesystem (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly maintain a Linux filesystem using system utilities. This objective includes manipulating standard filesystems and monitoring SMART devices.
|}

'''Key Knowledge Areas:'''

* Tools and utilities to manipulate and ext2, ext3 and ext4

* Tools and utilities to manipulate xfs

* Awareness of Btrfs

'''The following is a partial list of the used files, terms and utilities:'''

* fsck (fsck.*)

* mkfs (mkfs.*)

* dumpe2fs, xfsdump, xfsrestore

* debugfs

* tune2fs

* mkswap

* xfs_info, xfs_check and xfs_repair

* smartd, smartctl

 

====203.3 Creating and configuring filesystem options (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure automount filesystems using AutoFS. This objective includes configuring automount for network and device filesystems. Also included is creating filesystems for devices such as CD-ROMs and a basic feature knowledge of encrypted filesystems.
|}

'''Key Knowledge Areas:'''

* autofs configuration files

* UDF and ISO9660 tools and utilities

* awareness of CD-ROM filesystems (UDF, ISO9660, HFS)

* awareness of CD-ROM filesystem extensions (Joliet, Rock Ridge, El Torito)

* basic feature knowledge of encrypted filesystems

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/auto.master

* /etc/auto.[dir]

* mkisofs

 
 

===''Topic 204: Advanced Storage Device Administration''===

====204.1 Configuring RAID (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure and implement software RAID. This objective includes using and configuring RAID 0, 1 and 5.
|}

'''Key Knowledge Areas:'''

* Software RAID configuration files and utilities

'''The following is a partial list of the used files, terms and utilities:'''

* mdadm.conf

* mdadm

* /proc/mdstat

* partition type 0xFD

 

====204.2 Adjusting Storage Device Access (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure kernel options to support various drives. This objective includes software tools to view & modify hard disk settings including iSCSI devices.
|}

'''Key Knowledge Areas:'''

* Tools and utilities to configure DMA for IDE devices including ATAPI and SATA

* Tools and utilities to manipulate or analyse system resources (e.g. interrupts)

* Awareness of sdparm command and its uses

* Tools and utilities for iSCSI

'''The following is a partial list of the used files, terms and utilities:'''

* hdparm, sdparm

* tune2fs

* sysctl

* /dev/hd* & /dev/sd*

* iscsiadm, iscsid and iscsid.conf

* WWNN, WWPN, WWN, LUN numbers
 

====204.3 Logical Volume Manager (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to create and remove logical volumes, volume groups, and physical volumes. This objective includes snapshots and resizing logical volumes.
|}

'''Key Knowledge Areas:'''

* Tools in the LVM suite

* Resizing, renaming, creating, and removing logical volumes, volume groups, and physical volumes

* Creating and maintaining snapshots

* Activating volume groups

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/pv*

* /sbin/lv*

* /sbin/vg*

* mount

* /dev/mapper/

 
 

===''Topic 205: Networking Configuration''===

====205.1 Basic networking configuration (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a network device to be able to connect to a local, wired or wireless, and a wide-area network. This objective includes being able to communicate between various subnets within a single network including both IPv4 and IPv6 networks.
|}

'''Key Knowledge Areas:'''

* Utilities to configure and manipulate ethernet network interfaces

* Configuring wireless networks

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/route

* /sbin/ifconfig

* /sbin/ip

* /usr/sbin/arp

* /sbin/iwconfig

* /sbin/iwlist

 

====205.2 Advanced Network Configuration (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a network device to implement various network authentication schemes. This objective includes configuring a multi-homed network device and resolving communication problems.
|}

'''Key Knowledge Areas:'''

* Utilities to manipulate routing tables

* Utilities to configure and manipulate ethernet network interfaces

* Utilities to analyse the status of the network devices

* Utilities to monitor and analyse the TCP/IP traffic

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/route

* /sbin/ifconfig

* /bin/netstat

* /bin/ping

* /usr/sbin/arp

* /usr/sbin/tcpdump

* /usr/sbin/lsof

* /usr/bin/nc

* /sbin/ip

* nmap

 

====205.3 Troubleshooting network issues (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to identify and correct common network setup issues, to include knowledge of locations for basic configuration files and commands.
|}

'''Key Knowledge Areas:'''

* Location and content of access restriction files

* Utilities to configure and manipulate ethernet network interfaces

* Utilities to manage routing tables

* Utilities to list network states.

* Utilities to gain information about the network configuration

* Methods of information about the recognised and used hardware devices

* System initialisation files and their contents (SysV init process)

* Awareness of NetworkManager and its impact on network configuration

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/ifconfig

* /sbin/route

* /bin/netstat

* /etc/network || /etc/sysconfig/network-scripts/

* System log files such as /var/log/syslog & /var/log/messages

* /bin/ping

* /etc/resolv.conf

* /etc/hosts

* /etc/hostname | /etc/HOSTNAME

* /bin/hostname

* /usr/sbin/traceroute

* /bin/dmesg

* /etc/hosts.allow, /etc/hosts.deny

 
 

===''Topic 206: System Maintenance''===

====206.1 Make and install programs from source (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to build and install an executable program from source. This objective includes being able to unpack a file of sources.
|}

'''Key Knowledge Areas:'''

* Unpack source code using common compression and archive utilities.

* Understand basics of invoking make to compile programs.

* Apply parameters to a configure script.

* Know where sources are stored by default.

'''The following is a partial list of the used files, terms and utilities:'''

* /usr/src/

* gunzip

* gzip

* bzip2

* tar

* configure

* make

* uname

* install

* patch

 

====206.2 Backup operations (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to use system tools to back up important system data.
|}

'''Key Knowledge Areas:'''

* Knowledge about directories that have to be include in backups

* Awareness of network backup solutions such as Amanda, Bacula and BackupPC

* Knowledge of the benefits and drawbacks of tapes, CDR, disk or other backup media

* Perform partial and manual backups.

* Verify the integrity of backup files.

* Partially or fully restore backups.

'''The following is a partial list of the used files, terms and utilities:'''

* /bin/sh

* dd

* tar

* /dev/st* and /dev/nst*

* mt

* rsync

 

====206.3 Notify users on system-related issues (weight: 1)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to notify the users about current issues related to the system.
|}

'''Key Knowledge Areas:'''

* Automate communication with users through logon messages.

* Inform active users of system maintenance

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/issue

* /etc/issue.net

* /etc/motd

* wall

* /sbin/shutdown

 
 

==Objectives: Exam 202==

===''Topic 207: Domain Name Server''===

====207.1 Basic DNS server configuration (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure BIND to function as a caching-only DNS server. This objective includes the ability to convert older BIND configuration files to newer format, managing a running server and configuring logging.
|}

'''Key Knowledge Areas:'''

* BIND 9.x configuration files, terms and utilities

* Defining the location of the BIND zone files in BIND configuration files

* Reloading modified configuration and zone files

* Awareness of dnsmasq, djbdns and PowerDNS as alternate name servers

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/named.conf

* /var/named/*

* /usr/sbin/rndc

* kill

* host

* dig

 

====207.2 Create and maintain DNS zones (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to create a zone file for a forward or reverse zone or root level server. This objective includes setting appropriate values for records, adding hosts in zones and adding zones to the DNS. A candidate should also be able to delegate zones to another DNS server.
|}

'''Key Knowledge Areas:'''

* BIND 9 configuration files, terms and utilities

* Utilities to request information from the DNS server

* Layout, content and file location of the BIND zone files

* Various methods to add a new host in the zone files, including reverse zones

'''The following is a partial list of the used files, terms and utilities:'''

* /var/named/*

* zone file syntax

* resource record formats

* dig

* nslookup

* host

 

====207.3 Securing a DNS server (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a DNS server to run as a non-root user and run in a chroot jail. This objective includes secure exchange of data between DNS servers.
|}

'''Key Knowledge Areas:'''

* BIND 9 configuration files

* Configuring BIND to run in a chroot jail

* Split configuration of BIND using the forwarders statement

* Configuring and using transaction signatures (TSIG)

* Awareness of DNSSEC and basic tools

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/named.conf

* /etc/passwd

* DNSSEC

* dnssec-keygen

* dnssec-signzone

 
 

===''Topic 208: Web Services''===

====208.1 Basic Apache configuration (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure a web server. This objective includes monitoring the server's load and performance, restricting client user access, configuring support for scripting languages as modules and setting up client user authentication. Also included is configuring server options to restrict usage of resources. Candidates should be able to configure a web server to use virtual hosts and customise file access.
|}

'''Key Knowledge Areas:'''

* Apache 2.x configuration files, terms and utilities

* Apache log files configuration and content

* Access restriction methods and files

* mod_perl and PHP configuration

* Client user authentication files and utilities

* Configuration of maximum requests, minimum and maximum servers and clients

* Apache 2.x virtual host implementation (with and without dedicated IP addresses)

* Using redirect statements in Apache's configuration files to customise file access

'''The following is a partial list of the used files, terms and utilities:'''

* access logs and error logs

* .htaccess

* httpd.conf

* mod_auth

* htpasswd

* htgroup

* apache2ctl

* httpd

 

====208.2 Apache configuration for HTTPS (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a web server to provide HTTPS.
|}

'''Key Knowledge Areas:'''

* SSL configuration files, tools and utilities

* Ability to generate a server private key and CSR for a commercial CA

* Ability to generate a self-signed Certificate from private CA

* Ability to install the key and Certificate

* Awareness of the issues with Virtual Hosting and use of SSL

* Security issues in SSL use

'''The following is a partial list of the used files, terms and utilities:'''

* Apache2 configuration files

* /etc/ssl/*, /etc/pki/*

* openssl, CA.pl

* SSLEngine, SSLCertificateKeyFile, SSLCertificateFile, SSLCertificateChainFile

* SSLCACertificateFile, SSLCACertificatePath

* SSLProtocol, SSLCipherSuite, ServerTokens, ServerSignature, TraceEnable

 

====208.3 Implementing Squid as a caching proxy (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure a proxy server, including access policies, authentication and resource usage.
|}

'''Key Knowledge Areas:'''

* Squid 3.x configuration files, terms and utilities

* Access restriction methods

* Client user authentication methods

* Layout and content of ACL in the Squid configuration files

'''The following is a partial list of the used files, terms and utilities:'''

* squid.conf

* acl

* http_access

 

====208.4 Implementing Nginx as a web server and a reverse proxy (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure a reverse proxy server, Nginx. Basic configuration of Nginx as a HTTP server is included.
|}

'''Key Knowledge Areas:'''

* Nginx

* Reverse Proxy

* Basic Web Server

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/nginx/

* nginx

 
 

===''Topic 209: File Sharing''===

====209.1 Samba Server Configuration (weight: 5)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 5
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to set up a SAMBA server for various clients. This objective includes setting up Samba for login clients and setting up the workgroup in which a server participates and defining shared directories and printers. Also covered is a configuring a Linux client to use a Samba server. Troubleshooting installations is also tested.
|}

'''Key Knowledge Areas:'''

* Samba version 3 documentation

* Samba configuration files

* Samba tools and utilities

* Mounting Samba shares on Linux

* Samba daemons

* Mapping Windows user names to Linux user names

* User-Level and Share-Level security

'''The following is a partial list of the used files, terms and utilities:'''

* smbd, nmbd

* smbstatus, testparm, smbpasswd, nmblookup

* smbclient

* net

* /etc/smb/*

* /var/log/samba/

 

====209.2 NFS Server Configuration (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to export filesystems using NFS. This objective includes access restrictions, mounting an NFS filesystem on a client and securing NFS.
|}

'''Key Knowledge Areas:'''

* NFS version 3 configuration files

* NFS tools and utilities

* Access restrictions to certain hosts and/or subnets

* Mount options on server and client

* TCP Wrappers

* Awareness of NFSv4

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/exports

* exportfs

* showmount

* nfsstat

* /proc/mounts

* /etc/fstab

* rpcinfo

* mountd

* portmapper

 
 

===''Topic 210: Network Client Management''===

====210.1 DHCP configuration (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a DHCP server. This objective includes setting default and per client options, adding static hosts and BOOTP hosts. Also included is configuring a DHCP relay agent and maintaining the DHCP server.
|}

'''Key Knowledge Areas:'''

* DHCP configuration files, terms and utilities

* Subnet and dynamically-allocated range setup

'''The following is a partial list of the used files, terms and utilities:'''

* dhcpd.conf

* dhcpd.leases

* /var/log/daemon.log and /var/log/messages

* arp

* dhcpd

 

====210.2 PAM authentication (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | The candidate should be able to configure PAM to support authentication using various available methods.
|}

'''Key Knowledge Areas:'''

* PAM configuration files, terms and utilities

* passwd and shadow passwords

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/pam.d

* pam.conf

* nsswitch.conf

* pam_unix, pam_cracklib, pam_limits, pam_listfile

 

====210.3 LDAP client usage (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to perform queries and updates to an LDAP server. Also included is importing and adding items, as well as adding and managing users.
|}

'''Key Knowledge Areas:'''

* LDAP utilities for data management and queries

* Change user passwords

* Querying the LDAP directory

'''The following is a partial list of the used files, terms and utilities:'''

* ldapsearch

* ldappasswd

* ldapadd

* ldapdelete

 

====210.4 Configuring an OpenLDAP server (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a basic OpenLDAP server including knowledge of LDIF format and essential access controls. An understanding of the role of SSSD in authentication and identity management is included.
|}

'''Key Knowledge Areas:'''

* OpenLDAP

* Access Control

* Distinguished Names

* Changetype Operations

* Schemas and Whitepages

* Directories

* Object IDs, Attributes and Classes

* Awareness of System Security Services Daemon (SSSD)

'''The following is a partial list of the used files, terms and utilities:'''

* slapd

* slapd.conf

* LDIF

* slapadd

* slapcat

* slapindex

* /var/lib/ldap/*

* loglevel

 
 

===''Topic 211: E-Mail Services''===

====211.1 Using e-mail servers (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to manage an e-mail server, including the configuration of e-mail aliases, e-mail quotas and virtual e-mail domains. This objective includes configuring internal e-mail relays and monitoring e-mail servers.
|}

'''Key Knowledge Areas:'''

* Configuration files for postfix

* Basic knowledge of the SMTP protocol

* Awareness of sendmail and exim

'''The following is a partial list of the used files, terms and utilities:'''

* Configuration files and commands for postfix

* /etc/postfix/*

* /var/spool/postfix

* sendmail emulation layer commands

* /etc/aliases

* mail-related logs in /var/log/

 

====211.2 Managing Local E-Mail Delivery (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to implement client e-mail management software to filter, sort and monitor incoming user e-mail.
|}

'''Key Knowledge Areas:'''

* procmail configuration files, tools and utilities

* Usage of procmail on both server and client side

'''The following is a partial list of the used files, terms and utilities:'''

* ~/.procmailrc

* /etc/procmailrc

* procmail

* mbox and Maildir formats

 

====211.3 Managing Remote E-Mail Delivery (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure POP and IMAP daemons.
|}

'''Key Knowledge Areas:'''

* Courier IMAP and Courier POP configuration

* Dovecot configuration

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/courier/*

* dovecot.conf

 
 

===''Topic 212: System Security''===

====212.1 Configuring a router (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a system to perform network address translation (NAT, IP masquerading) and state its significance in protecting a network. This objective includes configuring port redirection, managing filter rules and averting attacks.
|}

'''Key Knowledge Areas:'''

* iptables configuration files, tools and utilities

* Tools, commands and utilities to manage routing tables.

* Private address ranges

* Port redirection and IP forwarding

* List and write filtering and rules that accept or block datagrams based on source or destination protocol, port and address

* Save and reload filtering configurations

* Awareness of ip6tables and filtering

'''The following is a partial list of the used files, terms and utilities:'''

* /proc/sys/net/ipv4

* /etc/services

* iptables

 

====212.2 Managing FTP servers (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure an FTP server for anonymous downloads and uploads. This objective includes precautions to be taken if anonymous uploads are permitted and configuring user access.
|}

'''Key Knowledge Areas:'''

* Configuration files, tools and utilities for Pure-FTPd and vsftpd

* Awareness of ProFTPd

* Understanding of passive vs. active FTP connections

'''The following is a partial list of the used files, terms and utilities:'''

* vsftpd.conf

* important Pure-FTPd command line options

 

====212.3 Secure shell (SSH) (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure and secure an SSH daemon. This objective includes managing keys and configuring SSH for users. Candidates should also be able to forward an application protocol over SSH and manage the SSH login.
|}

'''Key Knowledge Areas:'''

* OpenSSH configuration files, tools and utilities

* Login restrictions for the superuser and the normal users

* Managing and using server and client keys to login with and without password

* Usage of multiple connections from multiple hosts to guard against loss of connection to remote host following configuration changes

'''The following is a partial list of the used files, terms and utilities:'''

* ssh

* sshd

* /etc/ssh/sshd_config

* /etc/ssh/*

* Private and public key files

* PermitRootLogin, PubKeyAuthentication, AllowUsers, PasswordAuthentication, Protocol

 

====212.4 Security tasks (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to receive security alerts from various sources, install, configure and run intrusion detection systems and apply security patches and bugfixes.
|}

'''Key Knowledge Areas:'''

* Tools and utilities to scan and test ports on a server

* Locations and organisations that report security alerts as Bugtraq, CERT, CIAC or other sources

* Tools and utilities to implement an intrusion detection system (IDS)

* Awareness of OpenVAS and Snort

'''The following is a partial list of the used files, terms and utilities:'''

* telnet

* nmap

* fail2ban

* nc

* iptables

 

====212.5 OpenVPN (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a VPN (Virtual Private Network) and create secure point-to-point or site-to-site connections.
|}

'''Key Knowledge Areas:'''

* OpenVPN

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/openvpn/*

* openvpn

 
 

==Future Change Considerations==

Future changes to the objective will/may include:

* EFI shell, gdisk, parted not included. More appropriate in LPIC-1 update.

* lighttpd would have been too much coverage of web services. Perhaps reduce Apache next revision to make room.

* host level IDS (tripwire, AIDE, etc) to be covered in future LPIC-1.

* sieve and maildrop to be considered in a future update.

* SAN, AoE, and FCoE to be considered in a future update.

* encrypted file systems are covered in-depth in LPI-303 exam.

LPIC-2 Objectives V4

2013-06-12T13:03:30Z

StarnixAdmin: /* 202.3 Alternate Bootloaders (weight: 1) */

__FORCETOC__
==Overview of Tasks==

This is a required exam for LPI certification Level 2. It covers advanced skills for the Linux professional that are common across all distributions of Linux.

To pass LPIC-2, the candidate should be able to:

* Administer a small to medium-sized site
* Plan, implement, maintain, keep consistent, secure, and troubleshoot a small mixed (MS, Linux) network, including a:
** LAN server (Samba, NFS, DNS, DHCP, client management)
** Internet Gateway (firewall, VPN, SSH, web cache/proxy, mail)
** Internet Server (web server and reverse proxy, FTP server)
* Supervise assistants
* Advise management on automation and purchases

 

==Version Information==

These objectives are version 4.0.0. This version is to go live on Oct 1, 2013.

This is also a [[LPIC2SummaryVersion3To4|summary and detailed information]] on the changes from version 3.5.x to 4.0.0 of the objectives.

The [[LPIC-2_Objectives_V3|version 3.x of the LPIC-2 Objectives]] are still online.
 

==Addenda==

===''Version Update (Oct 1st, 2013)''===

* updated to version 4.0.0

 

==Translations of Objectives==

The following translations of the objectives are available on this wiki:

* [[LPIC-2_Objectives|English]]

* [[LPIC-2_Objectives(ES)|Spanish]]

* [[LPIC-2_Objectives(RU)|Russian]]

* [[LPIC-2_Objectives(Greek)|Greek]]

* [[LPIC-2_Objectives(Turkish)|Turkish]]

* [[LPIC-2_Objectives(FR)|French]]

 

==Objectives: Exam 201==

===''Topic 200: Capacity Planning''===

====200.1 Measure and Troubleshoot Resource Usage (weight: 6)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 6
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Candidates should be able to measure hardware resource and network bandwidth, identify and troubleshoot resource problems.

|}

'''Key Knowledge Areas:'''

* Measure CPU usage.

* Measure memory usage.

* Measure disk I/O.

* Measure network I/O.

* Measure firewalling and routing throughput.

* Map client bandwidth usage.

* Match / correlate system symptoms with likely problems.

* Estimate throughput and identify bottlenecks in a system including networking.

'''The following is a partial list of the used files, terms and utilities:'''

* iostat

* vmstat

* netstat

* pstree, ps

* w

* lsof

* top

* uptime

* sar

* swap

* processes blocked on I/O

* blocks in

* blocks out

 

====200.2 Predict Future Resource Needs (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Candidates should be able to monitor resource usage to predict future resource needs.

|}

'''Key Knowledge Areas:'''

* Use collectd to monitor IT infrastructure usage.

* Predict capacity break point of a configuration.

* Observe growth rate of capacity usage.

* Graph the trend of capacity usage.

* Awareness of monitoring solutions such as Nagios, MRTG and Cacti

'''The following is a partial list of the used files, terms and utilities:'''

* diagnose

* predict growth

* resource exhaustion

 
 

===''Topic 201: Linux Kernel''===

====201.1 Kernel components (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to utilise kernel components that are necessary to specific hardware, hardware drivers, system resources and requirements. This objective includes implementing different types of kernel images, understanding stable and longterm kernels and patches, as well as using kernel modules.
|}

'''Key Knowledge Areas:'''

* Kernel 2.6.x documentation

* Kernel 3.x documentation

'''The following is a partial list of the used files, terms and utilities:'''

* /usr/src/linux

* /usr/src/linux/Documentation

* zImage

* bzImage

 

====201.2 Compiling a Linux kernel (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly configure a kernel to include or disable specific features of the Linux kernel as necessary. This objective includes compiling and recompiling the Linux kernel as needed, updating and noting changes in a new kernel, creating an initrd image and installing new kernels.
|}

'''Key Knowledge Areas:'''

* /usr/src/linux/

* Kernel Makefiles

* Kernel 2.6.x/3.x make targets

* Customize the current kernel configuration.

* Build a new kernel and appropriate kernel modules.

* Install a new kernel and any modules.

* Ensure that the boot manager can locate the new kernel and associated files.

* Module configuration files

* Awareness of dracut

'''The following is a partial list of the used files, terms and utilities:'''

* mkinitrd

* mkinitramfs

* make

* make targets (all, config, xconfig, menuconfig, gconfig, oldconfig, mrproper, zImage, bzImage, modules, modules_install, rpm-pkg, binrpm-pkg, deb-pkg)

* gzip

* bzip2

* module tools

* /usr/src/linux/.config

* /lib/modules/kernel-version/*

* depmod

 

====201.3 Kernel runtime management and troubleshooting (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to manage and/or query a 2.6.x or 3.x kernel and its loadable modules. Candidates should be able to identify and correct common boot and run time issues. Candidates should understand device detection and management using udev. This objective includes troubleshooting udev rules.
|}

'''Key Knowledge Areas:'''

* Use command-line utilities to get information about the currently running kernel and kernel modules.

* Manually load and unload kernel modules.

* Determine when modules can be unloaded.

* Determine what parameters a module accepts.

* Configure the system to load modules by names other than their file name.

* /proc filesystem

* Content of /, /boot , and /lib/modules

* Tools and utilities to analyse information about the available hardware

* udev rules

'''The following is a partial list of the used files, terms and utilities:'''

* /lib/modules/kernel-version/modules.dep

* module configuration files in /etc

* /proc/sys/kernel/

* /sbin/depmod

* /sbin/rmmod

* /sbin/modinfo

* /bin/dmesg

* /sbin/lspci

* /usr/bin/lsdev

* /sbin/lsmod

* /sbin/modprobe

* /sbin/insmod

* /bin/uname

* /usr/bin/lsusb

* /etc/sysctl.conf, /etc/sysctl.d/

* /sbin/sysctl

* udevmonitor

* /etc/udev

 
 

===''Topic 202: System Startup''===

====202.1 Customising SysV-init system startup (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to query and modify the behaviour of system services at various run levels. A thorough understanding of the init structure and boot process is required. This objective includes interacting with run levels.
|}

'''Key Knowledge Areas:'''

* Linux Standard Base Specification (LSB)

* SysV init environment

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/inittab

* /etc/init.d/

* /etc/rc.d/

* chkconfig

* update-rc.d

* init and telinit

 

====202.2 System recovery (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly manipulate a Linux system during both the boot process and during recovery mode. This objective includes using both the init utility and init-related kernel options. Candidates should be able to determine the cause of errors in loading and usage of bootloaders. GRUB version 2 and GRUB Legacy are the bootloaders of interest.
|}

'''Key Knowledge Areas:'''

* GRUB version 2 and Legacy

* grub shell

* boot loader start and hand off to kernel

* kernel loading

* hardware initialisation and setup

* daemon/service initialisation and setup

* Know the different boot loader install locations on a hard disk or removable device

* Overwriting standard boot loader options and using boot loader shells

* Awareness of UEFI

'''The following is a partial list of the used files, terms and utilities:'''

* mount

* fsck

* inittab, telinit and init with SysV init

* The contents of /boot/ and /boot/grub/

* GRUB

* grub-install

* initrd, initramfs

* Master boot record

 

====202.3 Alternate Bootloaders (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be aware of other bootloaders and their major features.
|}

'''Key Knowledge Areas:'''

* LILO

* SYSLINUX, ISOLINUX, PXELINUX

* Understanding of PXE

'''The following is a partial list of the used files, terms and utilities:'''

* lilo, /etc/lilo.conf

* syslinux

* extlinux

* isolinux.bin

* isolinux.cfg

* pxelinux.0

* pxelinux.cfg/*

 
 

===''Topic 203: Filesystem and Devices''===

====203.1 Operating the Linux filesystem (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly configure and navigate the standard Linux filesystem. This objective includes configuring and mounting various filesystem types.
|}

'''Key Knowledge Areas:'''

* The concept of the fstab configuration

* Tools and utilities for handling SWAP partitions and files

* Use of UUIDs for identifying and mounting file systems

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/fstab

* /etc/mtab

* /proc/mounts

* mount and umount

* blkid

* sync

* swapon

* swapoff

 

====203.2 Maintaining a Linux filesystem (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly maintain a Linux filesystem using system utilities. This objective includes manipulating standard filesystems and monitoring SMART devices.
|}

'''Key Knowledge Areas:'''

* Tools and utilities to manipulate and ext2, ext3 and ext4

* Tools and utilities to manipulate xfs

* Awareness of Btrfs

'''The following is a partial list of the used files, terms and utilities:'''

* fsck (fsck.*)

* mkfs (mkfs.*)

* dumpe2fs, xfsdump, xfsrestore

* debugfs

* tune2fs

* mkswap

* xfs_info, xfs_check and xfs_repair

* smartd, smartctl

 

====203.3 Creating and configuring filesystem options (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure automount filesystems using AutoFS. This objective includes configuring automount for network and device filesystems. Also included is creating filesystems for devices such as CD-ROMs and a basic feature knowledge of encrypted filesystems.
|}

'''Key Knowledge Areas:'''

* autofs configuration files

* UDF and ISO9660 tools and utilities

* awareness of CD-ROM filesystems (UDF, ISO9660, HFS)

* awareness of CD-ROM filesystem extensions (Joliet, Rock Ridge, El Torito)

* basic feature knowledge of encrypted filesystems

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/auto.master

* /etc/auto.[dir]

* mkisofs

 
 

===''Topic 204: Advanced Storage Device Administration''===

====204.1 Configuring RAID (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure and implement software RAID. This objective includes using and configuring RAID 0, 1 and 5.
|}

'''Key Knowledge Areas:'''

* Software RAID configuration files and utilities

'''The following is a partial list of the used files, terms and utilities:'''

* mdadm.conf

* mdadm

* /proc/mdstat

* partition type 0xFD

 

====204.2 Adjusting Storage Device Access (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure kernel options to support various drives. This objective includes software tools to view & modify hard disk settings including iSCSI devices.
|}

'''Key Knowledge Areas:'''

* Tools and utilities to configure DMA for IDE devices including ATAPI and SATA

* Tools and utilities to manipulate or analyse system resources (e.g. interrupts)

* Awareness of sdparm command and its uses

* Tools and utilities for iSCSI

'''The following is a partial list of the used files, terms and utilities:'''

* hdparm, sdparm

* tune2fs

* sysctl

* /dev/hd* & /dev/sd*

* iscsiadm, iscsid and iscsid.conf

* WWNN, WWPN, WWN, LUN numbers
 

====204.3 Logical Volume Manager (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to create and remove logical volumes, volume groups, and physical volumes. This objective includes snapshots and resizing logical volumes.
|}

'''Key Knowledge Areas:'''

* Tools in the LVM suite

* Resizing, renaming, creating, and removing logical volumes, volume groups, and physical volumes

* Creating and maintaining snapshots

* Activating volume groups

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/pv*

* /sbin/lv*

* /sbin/vg*

* mount

* /dev/mapper/

 
 

===''Topic 205: Networking Configuration''===

====205.1 Basic networking configuration (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a network device to be able to connect to a local, wired or wireless, and a wide-area network. This objective includes being able to communicate between various subnets within a single network including both IPv4 and IPv6 networks.
|}

'''Key Knowledge Areas:'''

* Utilities to configure and manipulate ethernet network interfaces

* Configuring wireless networks

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/route

* /sbin/ifconfig

* /sbin/ip

* /usr/sbin/arp

* /sbin/iwconfig

* /sbin/iwlist

 

====205.2 Advanced Network Configuration (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a network device to implement various network authentication schemes. This objective includes configuring a multi-homed network device and resolving communication problems.
|}

'''Key Knowledge Areas:'''

* Utilities to manipulate routing tables

* Utilities to configure and manipulate ethernet network interfaces

* Utilities to analyse the status of the network devices

* Utilities to monitor and analyse the TCP/IP traffic

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/route

* /sbin/ifconfig

* /bin/netstat

* /bin/ping

* /usr/sbin/arp

* /usr/sbin/tcpdump

* /usr/sbin/lsof

* /usr/bin/nc

* /sbin/ip

* nmap

 

====205.3 Troubleshooting network issues (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to identify and correct common network setup issues, to include knowledge of locations for basic configuration files and commands.
|}

'''Key Knowledge Areas:'''

* Location and content of access restriction files

* Utilities to configure and manipulate ethernet network interfaces

* Utilities to manage routing tables

* Utilities to list network states.

* Utilities to gain information about the network configuration

* Methods of information about the recognised and used hardware devices

* System initialisation files and their contents (SysV init process)

* Awareness of NetworkManager and its impact on network configuration

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/ifconfig

* /sbin/route

* /bin/netstat

* /etc/network || /etc/sysconfig/network-scripts/

* System log files such as /var/log/syslog & /var/log/messages

* /bin/ping

* /etc/resolv.conf

* /etc/hosts

* /etc/hostname | /etc/HOSTNAME

* /bin/hostname

* /usr/sbin/traceroute

* /bin/dmesg

* /etc/hosts.allow, /etc/hosts.deny

 
 

===''Topic 206: System Maintenance''===

====206.1 Make and install programs from source (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to build and install an executable program from source. This objective includes being able to unpack a file of sources.
|}

'''Key Knowledge Areas:'''

* Unpack source code using common compression and archive utilities.

* Understand basics of invoking make to compile programs.

* Apply parameters to a configure script.

* Know where sources are stored by default.

'''The following is a partial list of the used files, terms and utilities:'''

* /usr/src/

* gunzip

* gzip

* bzip2

* tar

* configure

* make

* uname

* install

* patch

 

====206.2 Backup operations (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to use system tools to back up important system data.
|}

'''Key Knowledge Areas:'''

* Knowledge about directories that have to be include in backups

* Awareness of network backup solutions such as Amanda, Bacula and BackupPC

* Knowledge of the benefits and drawbacks of tapes, CDR, disk or other backup media

* Perform partial and manual backups.

* Verify the integrity of backup files.

* Partially or fully restore backups.

'''The following is a partial list of the used files, terms and utilities:'''

* /bin/sh

* dd

* tar

* /dev/st* and /dev/nst*

* mt

* rsync

 

====206.3 Notify users on system-related issues (weight: 1)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to notify the users about current issues related to the system.
|}

'''Key Knowledge Areas:'''

* Automate communication with users through logon messages.

* Inform active users of system maintenance

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/issue

* /etc/issue.net

* /etc/motd

* wall

* /sbin/shutdown

 
 

==Objectives: Exam 202==

===''Topic 207: Domain Name Server''===

====207.1 Basic DNS server configuration (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure BIND to function as a caching-only DNS server. This objective includes the ability to convert older BIND configuration files to newer format, managing a running server and configuring logging.
|}

'''Key Knowledge Areas:'''

* BIND 9.x configuration files, terms and utilities

* Defining the location of the BIND zone files in BIND configuration files

* Reloading modified configuration and zone files

* Awareness of dnsmasq, djbdns and PowerDNS as alternate name servers

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/named.conf

* /var/named/*

* /usr/sbin/rndc

* kill

* host

* dig

 

====207.2 Create and maintain DNS zones (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to create a zone file for a forward or reverse zone or root level server. This objective includes setting appropriate values for records, adding hosts in zones and adding zones to the DNS. A candidate should also be able to delegate zones to another DNS server.
|}

'''Key Knowledge Areas:'''

* BIND 9 configuration files, terms and utilities

* Utilities to request information from the DNS server

* Layout, content and file location of the BIND zone files

* Various methods to add a new host in the zone files, including reverse zones

'''The following is a partial list of the used files, terms and utilities:'''

* /var/named/*

* zone file syntax

* resource record formats

* dig

* nslookup

* host

 

====207.3 Securing a DNS server (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a DNS server to run as a non-root user and run in a chroot jail. This objective includes secure exchange of data between DNS servers.
|}

'''Key Knowledge Areas:'''

* BIND 9 configuration files

* Configuring BIND to run in a chroot jail

* Split configuration of BIND using the forwarders statement

* Configuring and using transaction signatures (TSIG)

* Awareness of DNSSEC and basic tools

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/named.conf

* /etc/passwd

* DNSSEC

* dnssec-keygen

* dnssec-signzone

 
 

===''Topic 208: Web Services''===

====208.1 Basic Apache configuration (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure a web server. This objective includes monitoring the server's load and performance, restricting client user access, configuring support for scripting languages as modules and setting up client user authentication. Also included is configuring server options to restrict usage of resources. Candidates should be able to configure a web server to use virtual hosts and customise file access.
|}

'''Key Knowledge Areas:'''

* Apache 2.x configuration files, terms and utilities

* Apache log files configuration and content

* Access restriction methods and files

* mod_perl and PHP configuration

* Client user authentication files and utilities

* Configuration of maximum requests, minimum and maximum servers and clients

* Apache 2.x virtual host implementation (with and without dedicated IP addresses)

* Using redirect statements in Apache's configuration files to customise file access

'''The following is a partial list of the used files, terms and utilities:'''

* access logs and error logs

* .htaccess

* httpd.conf

* mod_auth

* htpasswd

* htgroup

* apache2ctl

* httpd

 

====208.2 Apache configuration for HTTPS (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a web server to provide HTTPS.
|}

'''Key Knowledge Areas:'''

* SSL configuration files, tools and utilities

* Ability to generate a server private key and CSR for a commercial CA

* Ability to generate a self-signed Certificate from private CA

* Ability to install the key and Certificate

* Awareness of the issues with Virtual Hosting and use of SSL

* Security issues in SSL use

'''The following is a partial list of the used files, terms and utilities:'''

* Apache2 configuration files

* /etc/ssl/*, /etc/pki/*

* openssl, CA.pl

* SSLEngine, SSLCertificateKeyFile, SSLCertificateFile, SSLCertificateChainFile

* SSLCACertificateFile, SSLCACertificatePath

* SSLProtocol, SSLCipherSuite, ServerTokens, ServerSignature, TraceEnable

 

====208.3 Implementing Squid as a caching proxy (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure a proxy server, including access policies, authentication and resource usage.
|}

'''Key Knowledge Areas:'''

* Squid 3.x configuration files, terms and utilities

* Access restriction methods

* Client user authentication methods

* Layout and content of ACL in the Squid configuration files

'''The following is a partial list of the used files, terms and utilities:'''

* squid.conf

* acl

* http_access

 

====208.4 Implementing Nginx as a web server and a reverse proxy (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure a reverse proxy server, Nginx. Basic configuration of Nginx as a HTTP server is included.
|}

'''Key Knowledge Areas:'''

* Nginx

* Reverse Proxy

* Basic Web Server

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/nginx/

* nginx

 
 

===''Topic 209: File Sharing''===

====209.1 Samba Server Configuration (weight: 5)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 5
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to set up a SAMBA server for various clients. This objective includes setting up Samba for login clients and setting up the workgroup in which a server participates and defining shared directories and printers. Also covered is a configuring a Linux client to use a Samba server. Troubleshooting installations is also tested.
|}

'''Key Knowledge Areas:'''

* Samba version 3 documentation

* Samba configuration files

* Samba tools and utilities

* Mounting Samba shares on Linux

* Samba daemons

* Mapping Windows user names to Linux user names

* User-Level and Share-Level security

'''The following is a partial list of the used files, terms and utilities:'''

* smbd, nmbd

* smbstatus, testparm, smbpasswd, nmblookup

* smbclient

* net

* /etc/smb/*

* /var/log/samba/

 

====209.2 NFS Server Configuration (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to export filesystems using NFS. This objective includes access restrictions, mounting an NFS filesystem on a client and securing NFS.
|}

'''Key Knowledge Areas:'''

* NFS version 3 configuration files

* NFS tools and utilities

* Access restrictions to certain hosts and/or subnets

* Mount options on server and client

* TCP Wrappers

* Awareness of NFSv4

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/exports

* exportfs

* showmount

* nfsstat

* /proc/mounts

* /etc/fstab

* rpcinfo

* mountd

* portmapper

 
 

===''Topic 210: Network Client Management''===

====210.1 DHCP configuration (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a DHCP server. This objective includes setting default and per client options, adding static hosts and BOOTP hosts. Also included is configuring a DHCP relay agent and maintaining the DHCP server.
|}

'''Key Knowledge Areas:'''

* DHCP configuration files, terms and utilities

* Subnet and dynamically-allocated range setup

'''The following is a partial list of the used files, terms and utilities:'''

* dhcpd.conf

* dhcpd.leases

* /var/log/daemon.log and /var/log/messages

* arp

* dhcpd

 

====210.2 PAM authentication (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | The candidate should be able to configure PAM to support authentication using various available methods.
|}

'''Key Knowledge Areas:'''

* PAM configuration files, terms and utilities

* passwd and shadow passwords

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/pam.d

* pam.conf

* nsswitch.conf

* pam_unix, pam_cracklib, pam_limits, pam_listfile

 

====210.3 LDAP client usage (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to perform queries and updates to an LDAP server. Also included is importing and adding items, as well as adding and managing users.
|}

'''Key Knowledge Areas:'''

* LDAP utilities for data management and queries

* Change user passwords

* Querying the LDAP directory

'''The following is a partial list of the used files, terms and utilities:'''

* ldapsearch

* ldappasswd

* ldapadd

* ldapdelete

 

====210.4 Configuring an OpenLDAP server (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a basic OpenLDAP server including knowledge of LDIF format and essential access controls. An understanding of the role of SSSD in authentication and identity management is included.
|}

'''Key Knowledge Areas:'''

* OpenLDAP

* Access Control

* Distinguished Names

* Changetype Operations

* Schemas and Whitepages

* Directories

* Object IDs, Attributes and Classes

* Awareness of System Security Services Daemon (SSSD)

'''The following is a partial list of the used files, terms and utilities:'''

* slapd

* slapd.conf

* LDIF

* slapadd

* slapcat

* slapindex

* /var/lib/ldap/*

* loglevel

 
 

===''Topic 211: E-Mail Services''===

====211.1 Using e-mail servers (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to manage an e-mail server, including the configuration of e-mail aliases, e-mail quotas and virtual e-mail domains. This objective includes configuring internal e-mail relays and monitoring e-mail servers.
|}

'''Key Knowledge Areas:'''

* Configuration files for postfix

* Basic knowledge of the SMTP protocol

* Awareness of sendmail and exim

'''The following is a partial list of the used files, terms and utilities:'''

* Configuration files and commands for postfix

* /etc/postfix/*

* /var/spool/postfix

* sendmail emulation layer commands

* /etc/aliases

* mail-related logs in /var/log/

 

====211.2 Managing Local E-Mail Delivery (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to implement client e-mail management software to filter, sort and monitor incoming user e-mail.
|}

'''Key Knowledge Areas:'''

* procmail configuration files, tools and utilities

* Usage of procmail on both server and client side

'''The following is a partial list of the used files, terms and utilities:'''

* ~/.procmailrc

* /etc/procmailrc

* procmail

* mbox and Maildir formats

 

====211.3 Managing Remote E-Mail Delivery (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure POP and IMAP daemons.
|}

'''Key Knowledge Areas:'''

* Courier IMAP and Courier POP configuration

* Dovecot configuration

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/courier/*

* dovecot.conf

 
 

===''Topic 212: System Security''===

====212.1 Configuring a router (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a system to perform network address translation (NAT, IP masquerading) and state its significance in protecting a network. This objective includes configuring port redirection, managing filter rules and averting attacks.
|}

'''Key Knowledge Areas:'''

* iptables configuration files, tools and utilities

* Tools, commands and utilities to manage routing tables.

* Private address ranges

* Port redirection and IP forwarding

* List and write filtering and rules that accept or block datagrams based on source or destination protocol, port and address

* Save and reload filtering configurations

* Awareness of ip6tables and filtering

'''The following is a partial list of the used files, terms and utilities:'''

* /proc/sys/net/ipv4

* /etc/services

* iptables

 

====212.2 Managing FTP servers (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure an FTP server for anonymous downloads and uploads. This objective includes precautions to be taken if anonymous uploads are permitted and configuring user access.
|}

'''Key Knowledge Areas:'''

* Configuration files, tools and utilities for Pure-FTPd and vsftpd

* Awareness of ProFTPd

* Understanding of passive vs. active FTP connections

'''The following is a partial list of the used files, terms and utilities:'''

* vsftpd.conf

* important Pure-FTPd command line options

 

====212.3 Secure shell (SSH) (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure and secure an SSH daemon. This objective includes managing keys and configuring SSH for users. Candidates should also be able to forward an application protocol over SSH and manage the SSH login.
|}

'''Key Knowledge Areas:'''

* OpenSSH configuration files, tools and utilities

* Login restrictions for the superuser and the normal users

* Managing and using server and client keys to login with and without password

* Usage of multiple connections from multiple hosts to guard against loss of connection to remote host following configuration changes

'''The following is a partial list of the used files, terms and utilities:'''

* ssh

* sshd

* /etc/ssh/sshd_config

* /etc/ssh/*

* Private and public key files

* PermitRootLogin, PubKeyAuthentication, AllowUsers, PasswordAuthentication, Protocol

 

====212.4 Security tasks (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to receive security alerts from various sources, install, configure and run intrusion detection systems and apply security patches and bugfixes.
|}

'''Key Knowledge Areas:'''

* Tools and utilities to scan and test ports on a server

* Locations and organisations that report security alerts as Bugtraq, CERT, CIAC or other sources

* Tools and utilities to implement an intrusion detection system (IDS)

* Awareness of OpenVAS and Snort

'''The following is a partial list of the used files, terms and utilities:'''

* telnet

* nmap

* fail2ban

* nc

* iptables

 

====212.5 OpenVPN (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a VPN (Virtual Private Network) and create secure point-to-point or site-to-site connections.
|}

'''Key Knowledge Areas:'''

* OpenVPN

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/openvpn/*

* openvpn

 
 

==Future Change Considerations==

Future changes to the objective will/may include:

* EFI shell, gdisk, parted not included. More appropriate in LPIC-1 update.

* lighttpd would have been too much coverage of web services. Perhaps reduce Apache next revision to make room.

* host level IDS (tripwire, AIDE, etc) to be covered in future LPIC-1.

* sieve and maildrop to be considered in a future update.

* SAN, AoE, and FCoE to be considered in a future update.

* encrypted file systems are covered in-depth in LPI-303 exam.

LPIC-2 Objectives V4

2013-06-12T13:02:31Z

StarnixAdmin: /* Topic 200: Capacity Planning */

__FORCETOC__
==Overview of Tasks==

This is a required exam for LPI certification Level 2. It covers advanced skills for the Linux professional that are common across all distributions of Linux.

To pass LPIC-2, the candidate should be able to:

* Administer a small to medium-sized site
* Plan, implement, maintain, keep consistent, secure, and troubleshoot a small mixed (MS, Linux) network, including a:
** LAN server (Samba, NFS, DNS, DHCP, client management)
** Internet Gateway (firewall, VPN, SSH, web cache/proxy, mail)
** Internet Server (web server and reverse proxy, FTP server)
* Supervise assistants
* Advise management on automation and purchases

 

==Version Information==

These objectives are version 4.0.0. This version is to go live on Oct 1, 2013.

This is also a [[LPIC2SummaryVersion3To4|summary and detailed information]] on the changes from version 3.5.x to 4.0.0 of the objectives.

The [[LPIC-2_Objectives_V3|version 3.x of the LPIC-2 Objectives]] are still online.
 

==Addenda==

===''Version Update (Oct 1st, 2013)''===

* updated to version 4.0.0

 

==Translations of Objectives==

The following translations of the objectives are available on this wiki:

* [[LPIC-2_Objectives|English]]

* [[LPIC-2_Objectives(ES)|Spanish]]

* [[LPIC-2_Objectives(RU)|Russian]]

* [[LPIC-2_Objectives(Greek)|Greek]]

* [[LPIC-2_Objectives(Turkish)|Turkish]]

* [[LPIC-2_Objectives(FR)|French]]

 

==Objectives: Exam 201==

===''Topic 200: Capacity Planning''===

====200.1 Measure and Troubleshoot Resource Usage (weight: 6)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 6
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Candidates should be able to measure hardware resource and network bandwidth, identify and troubleshoot resource problems.

|}

'''Key Knowledge Areas:'''

* Measure CPU usage.

* Measure memory usage.

* Measure disk I/O.

* Measure network I/O.

* Measure firewalling and routing throughput.

* Map client bandwidth usage.

* Match / correlate system symptoms with likely problems.

* Estimate throughput and identify bottlenecks in a system including networking.

'''The following is a partial list of the used files, terms and utilities:'''

* iostat

* vmstat

* netstat

* pstree, ps

* w

* lsof

* top

* uptime

* sar

* swap

* processes blocked on I/O

* blocks in

* blocks out

 

====200.2 Predict Future Resource Needs (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Candidates should be able to monitor resource usage to predict future resource needs.

|}

'''Key Knowledge Areas:'''

* Use collectd to monitor IT infrastructure usage.

* Predict capacity break point of a configuration.

* Observe growth rate of capacity usage.

* Graph the trend of capacity usage.

* Awareness of monitoring solutions such as Nagios, MRTG and Cacti

'''The following is a partial list of the used files, terms and utilities:'''

* diagnose

* predict growth

* resource exhaustion

 
 

===''Topic 201: Linux Kernel''===

====201.1 Kernel components (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to utilise kernel components that are necessary to specific hardware, hardware drivers, system resources and requirements. This objective includes implementing different types of kernel images, understanding stable and longterm kernels and patches, as well as using kernel modules.
|}

'''Key Knowledge Areas:'''

* Kernel 2.6.x documentation

* Kernel 3.x documentation

'''The following is a partial list of the used files, terms and utilities:'''

* /usr/src/linux

* /usr/src/linux/Documentation

* zImage

* bzImage

 

====201.2 Compiling a Linux kernel (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly configure a kernel to include or disable specific features of the Linux kernel as necessary. This objective includes compiling and recompiling the Linux kernel as needed, updating and noting changes in a new kernel, creating an initrd image and installing new kernels.
|}

'''Key Knowledge Areas:'''

* /usr/src/linux/

* Kernel Makefiles

* Kernel 2.6.x/3.x make targets

* Customize the current kernel configuration.

* Build a new kernel and appropriate kernel modules.

* Install a new kernel and any modules.

* Ensure that the boot manager can locate the new kernel and associated files.

* Module configuration files

* Awareness of dracut

'''The following is a partial list of the used files, terms and utilities:'''

* mkinitrd

* mkinitramfs

* make

* make targets (all, config, xconfig, menuconfig, gconfig, oldconfig, mrproper, zImage, bzImage, modules, modules_install, rpm-pkg, binrpm-pkg, deb-pkg)

* gzip

* bzip2

* module tools

* /usr/src/linux/.config

* /lib/modules/kernel-version/*

* depmod

 

====201.3 Kernel runtime management and troubleshooting (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to manage and/or query a 2.6.x or 3.x kernel and its loadable modules. Candidates should be able to identify and correct common boot and run time issues. Candidates should understand device detection and management using udev. This objective includes troubleshooting udev rules.
|}

'''Key Knowledge Areas:'''

* Use command-line utilities to get information about the currently running kernel and kernel modules.

* Manually load and unload kernel modules.

* Determine when modules can be unloaded.

* Determine what parameters a module accepts.

* Configure the system to load modules by names other than their file name.

* /proc filesystem

* Content of /, /boot , and /lib/modules

* Tools and utilities to analyse information about the available hardware

* udev rules

'''The following is a partial list of the used files, terms and utilities:'''

* /lib/modules/kernel-version/modules.dep

* module configuration files in /etc

* /proc/sys/kernel/

* /sbin/depmod

* /sbin/rmmod

* /sbin/modinfo

* /bin/dmesg

* /sbin/lspci

* /usr/bin/lsdev

* /sbin/lsmod

* /sbin/modprobe

* /sbin/insmod

* /bin/uname

* /usr/bin/lsusb

* /etc/sysctl.conf, /etc/sysctl.d/

* /sbin/sysctl

* udevmonitor

* /etc/udev

 
 

===''Topic 202: System Startup''===

====202.1 Customising SysV-init system startup (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to query and modify the behaviour of system services at various run levels. A thorough understanding of the init structure and boot process is required. This objective includes interacting with run levels.
|}

'''Key Knowledge Areas:'''

* Linux Standard Base Specification (LSB)

* SysV init environment

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/inittab

* /etc/init.d/

* /etc/rc.d/

* chkconfig

* update-rc.d

* init and telinit

 

====202.2 System recovery (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly manipulate a Linux system during both the boot process and during recovery mode. This objective includes using both the init utility and init-related kernel options. Candidates should be able to determine the cause of errors in loading and usage of bootloaders. GRUB version 2 and GRUB Legacy are the bootloaders of interest.
|}

'''Key Knowledge Areas:'''

* GRUB version 2 and Legacy

* grub shell

* boot loader start and hand off to kernel

* kernel loading

* hardware initialisation and setup

* daemon/service initialisation and setup

* Know the different boot loader install locations on a hard disk or removable device

* Overwriting standard boot loader options and using boot loader shells

* Awareness of UEFI

'''The following is a partial list of the used files, terms and utilities:'''

* mount

* fsck

* inittab, telinit and init with SysV init

* The contents of /boot/ and /boot/grub/

* GRUB

* grub-install

* initrd, initramfs

* Master boot record

 

====202.3 Alternate Bootloaders (weight: 1)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be aware of other bootloaders and their major features.
|}

'''Key Knowledge Areas:'''

* LILO

* SYSLINUX, ISOLINUX, PXELINUX

* Understanding of PXE

'''The following is a partial list of the used files, terms and utilities:'''

* lilo, /etc/lilo.conf

* syslinux

* extlinux

* isolinux.bin

* isolinux.cfg

* pxelinux.0

* pxelinux.cfg/*

 
 

===''Topic 203: Filesystem and Devices''===

====203.1 Operating the Linux filesystem (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly configure and navigate the standard Linux filesystem. This objective includes configuring and mounting various filesystem types.
|}

'''Key Knowledge Areas:'''

* The concept of the fstab configuration

* Tools and utilities for handling SWAP partitions and files

* Use of UUIDs for identifying and mounting file systems

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/fstab

* /etc/mtab

* /proc/mounts

* mount and umount

* blkid

* sync

* swapon

* swapoff

 

====203.2 Maintaining a Linux filesystem (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly maintain a Linux filesystem using system utilities. This objective includes manipulating standard filesystems and monitoring SMART devices.
|}

'''Key Knowledge Areas:'''

* Tools and utilities to manipulate and ext2, ext3 and ext4

* Tools and utilities to manipulate xfs

* Awareness of Btrfs

'''The following is a partial list of the used files, terms and utilities:'''

* fsck (fsck.*)

* mkfs (mkfs.*)

* dumpe2fs, xfsdump, xfsrestore

* debugfs

* tune2fs

* mkswap

* xfs_info, xfs_check and xfs_repair

* smartd, smartctl

 

====203.3 Creating and configuring filesystem options (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure automount filesystems using AutoFS. This objective includes configuring automount for network and device filesystems. Also included is creating filesystems for devices such as CD-ROMs and a basic feature knowledge of encrypted filesystems.
|}

'''Key Knowledge Areas:'''

* autofs configuration files

* UDF and ISO9660 tools and utilities

* awareness of CD-ROM filesystems (UDF, ISO9660, HFS)

* awareness of CD-ROM filesystem extensions (Joliet, Rock Ridge, El Torito)

* basic feature knowledge of encrypted filesystems

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/auto.master

* /etc/auto.[dir]

* mkisofs

 
 

===''Topic 204: Advanced Storage Device Administration''===

====204.1 Configuring RAID (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure and implement software RAID. This objective includes using and configuring RAID 0, 1 and 5.
|}

'''Key Knowledge Areas:'''

* Software RAID configuration files and utilities

'''The following is a partial list of the used files, terms and utilities:'''

* mdadm.conf

* mdadm

* /proc/mdstat

* partition type 0xFD

 

====204.2 Adjusting Storage Device Access (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure kernel options to support various drives. This objective includes software tools to view & modify hard disk settings including iSCSI devices.
|}

'''Key Knowledge Areas:'''

* Tools and utilities to configure DMA for IDE devices including ATAPI and SATA

* Tools and utilities to manipulate or analyse system resources (e.g. interrupts)

* Awareness of sdparm command and its uses

* Tools and utilities for iSCSI

'''The following is a partial list of the used files, terms and utilities:'''

* hdparm, sdparm

* tune2fs

* sysctl

* /dev/hd* & /dev/sd*

* iscsiadm, iscsid and iscsid.conf

* WWNN, WWPN, WWN, LUN numbers
 

====204.3 Logical Volume Manager (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to create and remove logical volumes, volume groups, and physical volumes. This objective includes snapshots and resizing logical volumes.
|}

'''Key Knowledge Areas:'''

* Tools in the LVM suite

* Resizing, renaming, creating, and removing logical volumes, volume groups, and physical volumes

* Creating and maintaining snapshots

* Activating volume groups

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/pv*

* /sbin/lv*

* /sbin/vg*

* mount

* /dev/mapper/

 
 

===''Topic 205: Networking Configuration''===

====205.1 Basic networking configuration (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a network device to be able to connect to a local, wired or wireless, and a wide-area network. This objective includes being able to communicate between various subnets within a single network including both IPv4 and IPv6 networks.
|}

'''Key Knowledge Areas:'''

* Utilities to configure and manipulate ethernet network interfaces

* Configuring wireless networks

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/route

* /sbin/ifconfig

* /sbin/ip

* /usr/sbin/arp

* /sbin/iwconfig

* /sbin/iwlist

 

====205.2 Advanced Network Configuration (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a network device to implement various network authentication schemes. This objective includes configuring a multi-homed network device and resolving communication problems.
|}

'''Key Knowledge Areas:'''

* Utilities to manipulate routing tables

* Utilities to configure and manipulate ethernet network interfaces

* Utilities to analyse the status of the network devices

* Utilities to monitor and analyse the TCP/IP traffic

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/route

* /sbin/ifconfig

* /bin/netstat

* /bin/ping

* /usr/sbin/arp

* /usr/sbin/tcpdump

* /usr/sbin/lsof

* /usr/bin/nc

* /sbin/ip

* nmap

 

====205.3 Troubleshooting network issues (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to identify and correct common network setup issues, to include knowledge of locations for basic configuration files and commands.
|}

'''Key Knowledge Areas:'''

* Location and content of access restriction files

* Utilities to configure and manipulate ethernet network interfaces

* Utilities to manage routing tables

* Utilities to list network states.

* Utilities to gain information about the network configuration

* Methods of information about the recognised and used hardware devices

* System initialisation files and their contents (SysV init process)

* Awareness of NetworkManager and its impact on network configuration

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/ifconfig

* /sbin/route

* /bin/netstat

* /etc/network || /etc/sysconfig/network-scripts/

* System log files such as /var/log/syslog & /var/log/messages

* /bin/ping

* /etc/resolv.conf

* /etc/hosts

* /etc/hostname | /etc/HOSTNAME

* /bin/hostname

* /usr/sbin/traceroute

* /bin/dmesg

* /etc/hosts.allow, /etc/hosts.deny

 
 

===''Topic 206: System Maintenance''===

====206.1 Make and install programs from source (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to build and install an executable program from source. This objective includes being able to unpack a file of sources.
|}

'''Key Knowledge Areas:'''

* Unpack source code using common compression and archive utilities.

* Understand basics of invoking make to compile programs.

* Apply parameters to a configure script.

* Know where sources are stored by default.

'''The following is a partial list of the used files, terms and utilities:'''

* /usr/src/

* gunzip

* gzip

* bzip2

* tar

* configure

* make

* uname

* install

* patch

 

====206.2 Backup operations (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to use system tools to back up important system data.
|}

'''Key Knowledge Areas:'''

* Knowledge about directories that have to be include in backups

* Awareness of network backup solutions such as Amanda, Bacula and BackupPC

* Knowledge of the benefits and drawbacks of tapes, CDR, disk or other backup media

* Perform partial and manual backups.

* Verify the integrity of backup files.

* Partially or fully restore backups.

'''The following is a partial list of the used files, terms and utilities:'''

* /bin/sh

* dd

* tar

* /dev/st* and /dev/nst*

* mt

* rsync

 

====206.3 Notify users on system-related issues (weight: 1)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to notify the users about current issues related to the system.
|}

'''Key Knowledge Areas:'''

* Automate communication with users through logon messages.

* Inform active users of system maintenance

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/issue

* /etc/issue.net

* /etc/motd

* wall

* /sbin/shutdown

 
 

==Objectives: Exam 202==

===''Topic 207: Domain Name Server''===

====207.1 Basic DNS server configuration (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure BIND to function as a caching-only DNS server. This objective includes the ability to convert older BIND configuration files to newer format, managing a running server and configuring logging.
|}

'''Key Knowledge Areas:'''

* BIND 9.x configuration files, terms and utilities

* Defining the location of the BIND zone files in BIND configuration files

* Reloading modified configuration and zone files

* Awareness of dnsmasq, djbdns and PowerDNS as alternate name servers

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/named.conf

* /var/named/*

* /usr/sbin/rndc

* kill

* host

* dig

 

====207.2 Create and maintain DNS zones (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to create a zone file for a forward or reverse zone or root level server. This objective includes setting appropriate values for records, adding hosts in zones and adding zones to the DNS. A candidate should also be able to delegate zones to another DNS server.
|}

'''Key Knowledge Areas:'''

* BIND 9 configuration files, terms and utilities

* Utilities to request information from the DNS server

* Layout, content and file location of the BIND zone files

* Various methods to add a new host in the zone files, including reverse zones

'''The following is a partial list of the used files, terms and utilities:'''

* /var/named/*

* zone file syntax

* resource record formats

* dig

* nslookup

* host

 

====207.3 Securing a DNS server (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a DNS server to run as a non-root user and run in a chroot jail. This objective includes secure exchange of data between DNS servers.
|}

'''Key Knowledge Areas:'''

* BIND 9 configuration files

* Configuring BIND to run in a chroot jail

* Split configuration of BIND using the forwarders statement

* Configuring and using transaction signatures (TSIG)

* Awareness of DNSSEC and basic tools

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/named.conf

* /etc/passwd

* DNSSEC

* dnssec-keygen

* dnssec-signzone

 
 

===''Topic 208: Web Services''===

====208.1 Basic Apache configuration (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure a web server. This objective includes monitoring the server's load and performance, restricting client user access, configuring support for scripting languages as modules and setting up client user authentication. Also included is configuring server options to restrict usage of resources. Candidates should be able to configure a web server to use virtual hosts and customise file access.
|}

'''Key Knowledge Areas:'''

* Apache 2.x configuration files, terms and utilities

* Apache log files configuration and content

* Access restriction methods and files

* mod_perl and PHP configuration

* Client user authentication files and utilities

* Configuration of maximum requests, minimum and maximum servers and clients

* Apache 2.x virtual host implementation (with and without dedicated IP addresses)

* Using redirect statements in Apache's configuration files to customise file access

'''The following is a partial list of the used files, terms and utilities:'''

* access logs and error logs

* .htaccess

* httpd.conf

* mod_auth

* htpasswd

* htgroup

* apache2ctl

* httpd

 

====208.2 Apache configuration for HTTPS (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a web server to provide HTTPS.
|}

'''Key Knowledge Areas:'''

* SSL configuration files, tools and utilities

* Ability to generate a server private key and CSR for a commercial CA

* Ability to generate a self-signed Certificate from private CA

* Ability to install the key and Certificate

* Awareness of the issues with Virtual Hosting and use of SSL

* Security issues in SSL use

'''The following is a partial list of the used files, terms and utilities:'''

* Apache2 configuration files

* /etc/ssl/*, /etc/pki/*

* openssl, CA.pl

* SSLEngine, SSLCertificateKeyFile, SSLCertificateFile, SSLCertificateChainFile

* SSLCACertificateFile, SSLCACertificatePath

* SSLProtocol, SSLCipherSuite, ServerTokens, ServerSignature, TraceEnable

 

====208.3 Implementing Squid as a caching proxy (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure a proxy server, including access policies, authentication and resource usage.
|}

'''Key Knowledge Areas:'''

* Squid 3.x configuration files, terms and utilities

* Access restriction methods

* Client user authentication methods

* Layout and content of ACL in the Squid configuration files

'''The following is a partial list of the used files, terms and utilities:'''

* squid.conf

* acl

* http_access

 

====208.4 Implementing Nginx as a web server and a reverse proxy (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure a reverse proxy server, Nginx. Basic configuration of Nginx as a HTTP server is included.
|}

'''Key Knowledge Areas:'''

* Nginx

* Reverse Proxy

* Basic Web Server

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/nginx/

* nginx

 
 

===''Topic 209: File Sharing''===

====209.1 Samba Server Configuration (weight: 5)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 5
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to set up a SAMBA server for various clients. This objective includes setting up Samba for login clients and setting up the workgroup in which a server participates and defining shared directories and printers. Also covered is a configuring a Linux client to use a Samba server. Troubleshooting installations is also tested.
|}

'''Key Knowledge Areas:'''

* Samba version 3 documentation

* Samba configuration files

* Samba tools and utilities

* Mounting Samba shares on Linux

* Samba daemons

* Mapping Windows user names to Linux user names

* User-Level and Share-Level security

'''The following is a partial list of the used files, terms and utilities:'''

* smbd, nmbd

* smbstatus, testparm, smbpasswd, nmblookup

* smbclient

* net

* /etc/smb/*

* /var/log/samba/

 

====209.2 NFS Server Configuration (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to export filesystems using NFS. This objective includes access restrictions, mounting an NFS filesystem on a client and securing NFS.
|}

'''Key Knowledge Areas:'''

* NFS version 3 configuration files

* NFS tools and utilities

* Access restrictions to certain hosts and/or subnets

* Mount options on server and client

* TCP Wrappers

* Awareness of NFSv4

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/exports

* exportfs

* showmount

* nfsstat

* /proc/mounts

* /etc/fstab

* rpcinfo

* mountd

* portmapper

 
 

===''Topic 210: Network Client Management''===

====210.1 DHCP configuration (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a DHCP server. This objective includes setting default and per client options, adding static hosts and BOOTP hosts. Also included is configuring a DHCP relay agent and maintaining the DHCP server.
|}

'''Key Knowledge Areas:'''

* DHCP configuration files, terms and utilities

* Subnet and dynamically-allocated range setup

'''The following is a partial list of the used files, terms and utilities:'''

* dhcpd.conf

* dhcpd.leases

* /var/log/daemon.log and /var/log/messages

* arp

* dhcpd

 

====210.2 PAM authentication (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | The candidate should be able to configure PAM to support authentication using various available methods.
|}

'''Key Knowledge Areas:'''

* PAM configuration files, terms and utilities

* passwd and shadow passwords

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/pam.d

* pam.conf

* nsswitch.conf

* pam_unix, pam_cracklib, pam_limits, pam_listfile

 

====210.3 LDAP client usage (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to perform queries and updates to an LDAP server. Also included is importing and adding items, as well as adding and managing users.
|}

'''Key Knowledge Areas:'''

* LDAP utilities for data management and queries

* Change user passwords

* Querying the LDAP directory

'''The following is a partial list of the used files, terms and utilities:'''

* ldapsearch

* ldappasswd

* ldapadd

* ldapdelete

 

====210.4 Configuring an OpenLDAP server (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a basic OpenLDAP server including knowledge of LDIF format and essential access controls. An understanding of the role of SSSD in authentication and identity management is included.
|}

'''Key Knowledge Areas:'''

* OpenLDAP

* Access Control

* Distinguished Names

* Changetype Operations

* Schemas and Whitepages

* Directories

* Object IDs, Attributes and Classes

* Awareness of System Security Services Daemon (SSSD)

'''The following is a partial list of the used files, terms and utilities:'''

* slapd

* slapd.conf

* LDIF

* slapadd

* slapcat

* slapindex

* /var/lib/ldap/*

* loglevel

 
 

===''Topic 211: E-Mail Services''===

====211.1 Using e-mail servers (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to manage an e-mail server, including the configuration of e-mail aliases, e-mail quotas and virtual e-mail domains. This objective includes configuring internal e-mail relays and monitoring e-mail servers.
|}

'''Key Knowledge Areas:'''

* Configuration files for postfix

* Basic knowledge of the SMTP protocol

* Awareness of sendmail and exim

'''The following is a partial list of the used files, terms and utilities:'''

* Configuration files and commands for postfix

* /etc/postfix/*

* /var/spool/postfix

* sendmail emulation layer commands

* /etc/aliases

* mail-related logs in /var/log/

 

====211.2 Managing Local E-Mail Delivery (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to implement client e-mail management software to filter, sort and monitor incoming user e-mail.
|}

'''Key Knowledge Areas:'''

* procmail configuration files, tools and utilities

* Usage of procmail on both server and client side

'''The following is a partial list of the used files, terms and utilities:'''

* ~/.procmailrc

* /etc/procmailrc

* procmail

* mbox and Maildir formats

 

====211.3 Managing Remote E-Mail Delivery (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure POP and IMAP daemons.
|}

'''Key Knowledge Areas:'''

* Courier IMAP and Courier POP configuration

* Dovecot configuration

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/courier/*

* dovecot.conf

 
 

===''Topic 212: System Security''===

====212.1 Configuring a router (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a system to perform network address translation (NAT, IP masquerading) and state its significance in protecting a network. This objective includes configuring port redirection, managing filter rules and averting attacks.
|}

'''Key Knowledge Areas:'''

* iptables configuration files, tools and utilities

* Tools, commands and utilities to manage routing tables.

* Private address ranges

* Port redirection and IP forwarding

* List and write filtering and rules that accept or block datagrams based on source or destination protocol, port and address

* Save and reload filtering configurations

* Awareness of ip6tables and filtering

'''The following is a partial list of the used files, terms and utilities:'''

* /proc/sys/net/ipv4

* /etc/services

* iptables

 

====212.2 Managing FTP servers (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure an FTP server for anonymous downloads and uploads. This objective includes precautions to be taken if anonymous uploads are permitted and configuring user access.
|}

'''Key Knowledge Areas:'''

* Configuration files, tools and utilities for Pure-FTPd and vsftpd

* Awareness of ProFTPd

* Understanding of passive vs. active FTP connections

'''The following is a partial list of the used files, terms and utilities:'''

* vsftpd.conf

* important Pure-FTPd command line options

 

====212.3 Secure shell (SSH) (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure and secure an SSH daemon. This objective includes managing keys and configuring SSH for users. Candidates should also be able to forward an application protocol over SSH and manage the SSH login.
|}

'''Key Knowledge Areas:'''

* OpenSSH configuration files, tools and utilities

* Login restrictions for the superuser and the normal users

* Managing and using server and client keys to login with and without password

* Usage of multiple connections from multiple hosts to guard against loss of connection to remote host following configuration changes

'''The following is a partial list of the used files, terms and utilities:'''

* ssh

* sshd

* /etc/ssh/sshd_config

* /etc/ssh/*

* Private and public key files

* PermitRootLogin, PubKeyAuthentication, AllowUsers, PasswordAuthentication, Protocol

 

====212.4 Security tasks (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to receive security alerts from various sources, install, configure and run intrusion detection systems and apply security patches and bugfixes.
|}

'''Key Knowledge Areas:'''

* Tools and utilities to scan and test ports on a server

* Locations and organisations that report security alerts as Bugtraq, CERT, CIAC or other sources

* Tools and utilities to implement an intrusion detection system (IDS)

* Awareness of OpenVAS and Snort

'''The following is a partial list of the used files, terms and utilities:'''

* telnet

* nmap

* fail2ban

* nc

* iptables

 

====212.5 OpenVPN (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a VPN (Virtual Private Network) and create secure point-to-point or site-to-site connections.
|}

'''Key Knowledge Areas:'''

* OpenVPN

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/openvpn/*

* openvpn

 
 

==Future Change Considerations==

Future changes to the objective will/may include:

* EFI shell, gdisk, parted not included. More appropriate in LPIC-1 update.

* lighttpd would have been too much coverage of web services. Perhaps reduce Apache next revision to make room.

* host level IDS (tripwire, AIDE, etc) to be covered in future LPIC-1.

* sieve and maildrop to be considered in a future update.

* SAN, AoE, and FCoE to be considered in a future update.

* encrypted file systems are covered in-depth in LPI-303 exam.

File:Lpic flowchart july30 2013.jpg

2013-06-12T00:20:51Z

StarnixAdmin:

LPIC-2 Objectives V4

2013-06-11T23:33:50Z

StarnixAdmin:

__FORCETOC__
==Overview of Tasks==

This is a required exam for LPI certification Level 2. It covers advanced skills for the Linux professional that are common across all distributions of Linux.

To pass LPIC-2, the candidate should be able to:

* Administer a small to medium-sized site
* Plan, implement, maintain, keep consistent, secure, and troubleshoot a small mixed (MS, Linux) network, including a:
** LAN server (Samba, NFS, DNS, DHCP, client management)
** Internet Gateway (firewall, VPN, SSH, web cache/proxy, mail)
** Internet Server (web server and reverse proxy, FTP server)
* Supervise assistants
* Advise management on automation and purchases

 

==Version Information==

These objectives are version 4.0.0. This version is to go live on Oct 1, 2013.

This is also a [[LPIC2SummaryVersion3To4|summary and detailed information]] on the changes from version 3.5.x to 4.0.0 of the objectives.

The [[LPIC-2_Objectives_V3|version 3.x of the LPIC-2 Objectives]] are still online.
 

==Addenda==

===''Version Update (Oct 1st, 2013)''===

* updated to version 4.0.0

 

==Translations of Objectives==

The following translations of the objectives are available on this wiki:

* [[LPIC-2_Objectives|English]]

* [[LPIC-2_Objectives(ES)|Spanish]]

* [[LPIC-2_Objectives(RU)|Russian]]

* [[LPIC-2_Objectives(Greek)|Greek]]

* [[LPIC-2_Objectives(Turkish)|Turkish]]

* [[LPIC-2_Objectives(FR)|French]]

 

==Objectives: Exam 201==

===''Topic 200: Capacity Planning''===

====200.1 Measure Resource Usage (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Candidates should be able to measure hardware resource and network bandwidth usage.

|}

'''Key Knowledge Areas:'''

* Measure CPU usage.

* Measure memory usage.

* Measure disk I/O.

* Measure network I/O.

* Measure firewalling and routing throughput.

* Map client bandwidth usage.

'''The following is a partial list of the used files, terms and utilities:'''

* iostat

* vmstat

* netstat

* pstree, ps

* w

* lsof

* top

* uptime

* sar

 

====200.2 Troubleshoot Resource Problems (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Candidates should be able to identify and troubleshoot resource problems.

|}

'''Key Knowledge Areas:'''

* Match / correlate system symptoms with likely problems.

* Estimate throughput and identify bottlenecks in a system including networking.

'''The following is a partial list of the used files, terms and utilities:'''

* swap

* processes blocked on I/O

* blocks in

* blocks out

* network

 

====200.3 Predict Future Resource Needs (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Candidates should be able to monitor resource usage to predict future resource needs.

|}

'''Key Knowledge Areas:'''

* Use collectd to monitor IT infrastructure usage.

* Predict capacity break point of a configuration.

* Observe growth rate of capacity usage.

* Graph the trend of capacity usage.

* Awareness of monitoring solutions such as Nagios, MRTG and Cacti

'''The following is a partial list of the used files, terms and utilities:'''

* diagnose

* predict growth

* resource exhaustion

 
 

===''Topic 201: Linux Kernel''===

====201.1 Kernel components (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to utilise kernel components that are necessary to specific hardware, hardware drivers, system resources and requirements. This objective includes implementing different types of kernel images, understanding stable and longterm kernels and patches, as well as using kernel modules.
|}

'''Key Knowledge Areas:'''

* Kernel 2.6.x documentation

* Kernel 3.x documentation

'''The following is a partial list of the used files, terms and utilities:'''

* /usr/src/linux

* /usr/src/linux/Documentation

* zImage

* bzImage

 

====201.2 Compiling a Linux kernel (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly configure a kernel to include or disable specific features of the Linux kernel as necessary. This objective includes compiling and recompiling the Linux kernel as needed, updating and noting changes in a new kernel, creating an initrd image and installing new kernels.
|}

'''Key Knowledge Areas:'''

* /usr/src/linux/

* Kernel Makefiles

* Kernel 2.6.x/3.x make targets

* Customize the current kernel configuration.

* Build a new kernel and appropriate kernel modules.

* Install a new kernel and any modules.

* Ensure that the boot manager can locate the new kernel and associated files.

* Module configuration files

* Awareness of dracut

'''The following is a partial list of the used files, terms and utilities:'''

* mkinitrd

* mkinitramfs

* make

* make targets (all, config, xconfig, menuconfig, gconfig, oldconfig, mrproper, zImage, bzImage, modules, modules_install, rpm-pkg, binrpm-pkg, deb-pkg)

* gzip

* bzip2

* module tools

* /usr/src/linux/.config

* /lib/modules/kernel-version/*

* depmod

 

====201.3 Kernel runtime management and troubleshooting (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to manage and/or query a 2.6.x or 3.x kernel and its loadable modules. Candidates should be able to identify and correct common boot and run time issues. Candidates should understand device detection and management using udev. This objective includes troubleshooting udev rules.
|}

'''Key Knowledge Areas:'''

* Use command-line utilities to get information about the currently running kernel and kernel modules.

* Manually load and unload kernel modules.

* Determine when modules can be unloaded.

* Determine what parameters a module accepts.

* Configure the system to load modules by names other than their file name.

* /proc filesystem

* Content of /, /boot , and /lib/modules

* Tools and utilities to analyse information about the available hardware

* udev rules

'''The following is a partial list of the used files, terms and utilities:'''

* /lib/modules/kernel-version/modules.dep

* module configuration files in /etc

* /proc/sys/kernel/

* /sbin/depmod

* /sbin/rmmod

* /sbin/modinfo

* /bin/dmesg

* /sbin/lspci

* /usr/bin/lsdev

* /sbin/lsmod

* /sbin/modprobe

* /sbin/insmod

* /bin/uname

* /usr/bin/lsusb

* /etc/sysctl.conf, /etc/sysctl.d/

* /sbin/sysctl

* udevmonitor

* /etc/udev

 
 

===''Topic 202: System Startup''===

====202.1 Customising SysV-init system startup (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to query and modify the behaviour of system services at various run levels. A thorough understanding of the init structure and boot process is required. This objective includes interacting with run levels.
|}

'''Key Knowledge Areas:'''

* Linux Standard Base Specification (LSB)

* SysV init environment

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/inittab

* /etc/init.d/

* /etc/rc.d/

* chkconfig

* update-rc.d

* init and telinit

 

====202.2 System recovery (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly manipulate a Linux system during both the boot process and during recovery mode. This objective includes using both the init utility and init-related kernel options. Candidates should be able to determine the cause of errors in loading and usage of bootloaders. GRUB version 2 and GRUB Legacy are the bootloaders of interest.
|}

'''Key Knowledge Areas:'''

* GRUB version 2 and Legacy

* grub shell

* boot loader start and hand off to kernel

* kernel loading

* hardware initialisation and setup

* daemon/service initialisation and setup

* Know the different boot loader install locations on a hard disk or removable device

* Overwriting standard boot loader options and using boot loader shells

* Awareness of UEFI

'''The following is a partial list of the used files, terms and utilities:'''

* mount

* fsck

* inittab, telinit and init with SysV init

* The contents of /boot/ and /boot/grub/

* GRUB

* grub-install

* initrd, initramfs

* Master boot record

 

====202.3 Alternate Bootloaders (weight: 1)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be aware of other bootloaders and their major features.
|}

'''Key Knowledge Areas:'''

* LILO

* SYSLINUX, ISOLINUX, PXELINUX

* Understanding of PXE

'''The following is a partial list of the used files, terms and utilities:'''

* lilo, /etc/lilo.conf

* syslinux

* extlinux

* isolinux.bin

* isolinux.cfg

* pxelinux.0

* pxelinux.cfg/*

 
 

===''Topic 203: Filesystem and Devices''===

====203.1 Operating the Linux filesystem (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly configure and navigate the standard Linux filesystem. This objective includes configuring and mounting various filesystem types.
|}

'''Key Knowledge Areas:'''

* The concept of the fstab configuration

* Tools and utilities for handling SWAP partitions and files

* Use of UUIDs for identifying and mounting file systems

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/fstab

* /etc/mtab

* /proc/mounts

* mount and umount

* blkid

* sync

* swapon

* swapoff

 

====203.2 Maintaining a Linux filesystem (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly maintain a Linux filesystem using system utilities. This objective includes manipulating standard filesystems and monitoring SMART devices.
|}

'''Key Knowledge Areas:'''

* Tools and utilities to manipulate and ext2, ext3 and ext4

* Tools and utilities to manipulate xfs

* Awareness of Btrfs

'''The following is a partial list of the used files, terms and utilities:'''

* fsck (fsck.*)

* mkfs (mkfs.*)

* dumpe2fs, xfsdump, xfsrestore

* debugfs

* tune2fs

* mkswap

* xfs_info, xfs_check and xfs_repair

* smartd, smartctl

 

====203.3 Creating and configuring filesystem options (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure automount filesystems using AutoFS. This objective includes configuring automount for network and device filesystems. Also included is creating filesystems for devices such as CD-ROMs and a basic feature knowledge of encrypted filesystems.
|}

'''Key Knowledge Areas:'''

* autofs configuration files

* UDF and ISO9660 tools and utilities

* awareness of CD-ROM filesystems (UDF, ISO9660, HFS)

* awareness of CD-ROM filesystem extensions (Joliet, Rock Ridge, El Torito)

* basic feature knowledge of encrypted filesystems

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/auto.master

* /etc/auto.[dir]

* mkisofs

 
 

===''Topic 204: Advanced Storage Device Administration''===

====204.1 Configuring RAID (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure and implement software RAID. This objective includes using and configuring RAID 0, 1 and 5.
|}

'''Key Knowledge Areas:'''

* Software RAID configuration files and utilities

'''The following is a partial list of the used files, terms and utilities:'''

* mdadm.conf

* mdadm

* /proc/mdstat

* partition type 0xFD

 

====204.2 Adjusting Storage Device Access (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure kernel options to support various drives. This objective includes software tools to view & modify hard disk settings including iSCSI devices.
|}

'''Key Knowledge Areas:'''

* Tools and utilities to configure DMA for IDE devices including ATAPI and SATA

* Tools and utilities to manipulate or analyse system resources (e.g. interrupts)

* Awareness of sdparm command and its uses

* Tools and utilities for iSCSI

'''The following is a partial list of the used files, terms and utilities:'''

* hdparm, sdparm

* tune2fs

* sysctl

* /dev/hd* & /dev/sd*

* iscsiadm, iscsid and iscsid.conf

* WWNN, WWPN, WWN, LUN numbers
 

====204.3 Logical Volume Manager (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to create and remove logical volumes, volume groups, and physical volumes. This objective includes snapshots and resizing logical volumes.
|}

'''Key Knowledge Areas:'''

* Tools in the LVM suite

* Resizing, renaming, creating, and removing logical volumes, volume groups, and physical volumes

* Creating and maintaining snapshots

* Activating volume groups

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/pv*

* /sbin/lv*

* /sbin/vg*

* mount

* /dev/mapper/

 
 

===''Topic 205: Networking Configuration''===

====205.1 Basic networking configuration (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a network device to be able to connect to a local, wired or wireless, and a wide-area network. This objective includes being able to communicate between various subnets within a single network including both IPv4 and IPv6 networks.
|}

'''Key Knowledge Areas:'''

* Utilities to configure and manipulate ethernet network interfaces

* Configuring wireless networks

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/route

* /sbin/ifconfig

* /sbin/ip

* /usr/sbin/arp

* /sbin/iwconfig

* /sbin/iwlist

 

====205.2 Advanced Network Configuration (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a network device to implement various network authentication schemes. This objective includes configuring a multi-homed network device and resolving communication problems.
|}

'''Key Knowledge Areas:'''

* Utilities to manipulate routing tables

* Utilities to configure and manipulate ethernet network interfaces

* Utilities to analyse the status of the network devices

* Utilities to monitor and analyse the TCP/IP traffic

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/route

* /sbin/ifconfig

* /bin/netstat

* /bin/ping

* /usr/sbin/arp

* /usr/sbin/tcpdump

* /usr/sbin/lsof

* /usr/bin/nc

* /sbin/ip

* nmap

 

====205.3 Troubleshooting network issues (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to identify and correct common network setup issues, to include knowledge of locations for basic configuration files and commands.
|}

'''Key Knowledge Areas:'''

* Location and content of access restriction files

* Utilities to configure and manipulate ethernet network interfaces

* Utilities to manage routing tables

* Utilities to list network states.

* Utilities to gain information about the network configuration

* Methods of information about the recognised and used hardware devices

* System initialisation files and their contents (SysV init process)

* Awareness of NetworkManager and its impact on network configuration

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/ifconfig

* /sbin/route

* /bin/netstat

* /etc/network || /etc/sysconfig/network-scripts/

* System log files such as /var/log/syslog & /var/log/messages

* /bin/ping

* /etc/resolv.conf

* /etc/hosts

* /etc/hostname | /etc/HOSTNAME

* /bin/hostname

* /usr/sbin/traceroute

* /bin/dmesg

* /etc/hosts.allow, /etc/hosts.deny

 
 

===''Topic 206: System Maintenance''===

====206.1 Make and install programs from source (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to build and install an executable program from source. This objective includes being able to unpack a file of sources.
|}

'''Key Knowledge Areas:'''

* Unpack source code using common compression and archive utilities.

* Understand basics of invoking make to compile programs.

* Apply parameters to a configure script.

* Know where sources are stored by default.

'''The following is a partial list of the used files, terms and utilities:'''

* /usr/src/

* gunzip

* gzip

* bzip2

* tar

* configure

* make

* uname

* install

* patch

 

====206.2 Backup operations (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to use system tools to back up important system data.
|}

'''Key Knowledge Areas:'''

* Knowledge about directories that have to be include in backups

* Awareness of network backup solutions such as Amanda, Bacula and BackupPC

* Knowledge of the benefits and drawbacks of tapes, CDR, disk or other backup media

* Perform partial and manual backups.

* Verify the integrity of backup files.

* Partially or fully restore backups.

'''The following is a partial list of the used files, terms and utilities:'''

* /bin/sh

* dd

* tar

* /dev/st* and /dev/nst*

* mt

* rsync

 

====206.3 Notify users on system-related issues (weight: 1)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to notify the users about current issues related to the system.
|}

'''Key Knowledge Areas:'''

* Automate communication with users through logon messages.

* Inform active users of system maintenance

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/issue

* /etc/issue.net

* /etc/motd

* wall

* /sbin/shutdown

 
 

==Objectives: Exam 202==

===''Topic 207: Domain Name Server''===

====207.1 Basic DNS server configuration (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure BIND to function as a caching-only DNS server. This objective includes the ability to convert older BIND configuration files to newer format, managing a running server and configuring logging.
|}

'''Key Knowledge Areas:'''

* BIND 9.x configuration files, terms and utilities

* Defining the location of the BIND zone files in BIND configuration files

* Reloading modified configuration and zone files

* Awareness of dnsmasq, djbdns and PowerDNS as alternate name servers

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/named.conf

* /var/named/*

* /usr/sbin/rndc

* kill

* host

* dig

 

====207.2 Create and maintain DNS zones (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to create a zone file for a forward or reverse zone or root level server. This objective includes setting appropriate values for records, adding hosts in zones and adding zones to the DNS. A candidate should also be able to delegate zones to another DNS server.
|}

'''Key Knowledge Areas:'''

* BIND 9 configuration files, terms and utilities

* Utilities to request information from the DNS server

* Layout, content and file location of the BIND zone files

* Various methods to add a new host in the zone files, including reverse zones

'''The following is a partial list of the used files, terms and utilities:'''

* /var/named/*

* zone file syntax

* resource record formats

* dig

* nslookup

* host

 

====207.3 Securing a DNS server (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a DNS server to run as a non-root user and run in a chroot jail. This objective includes secure exchange of data between DNS servers.
|}

'''Key Knowledge Areas:'''

* BIND 9 configuration files

* Configuring BIND to run in a chroot jail

* Split configuration of BIND using the forwarders statement

* Configuring and using transaction signatures (TSIG)

* Awareness of DNSSEC and basic tools

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/named.conf

* /etc/passwd

* DNSSEC

* dnssec-keygen

* dnssec-signzone

 
 

===''Topic 208: Web Services''===

====208.1 Basic Apache configuration (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure a web server. This objective includes monitoring the server's load and performance, restricting client user access, configuring support for scripting languages as modules and setting up client user authentication. Also included is configuring server options to restrict usage of resources. Candidates should be able to configure a web server to use virtual hosts and customise file access.
|}

'''Key Knowledge Areas:'''

* Apache 2.x configuration files, terms and utilities

* Apache log files configuration and content

* Access restriction methods and files

* mod_perl and PHP configuration

* Client user authentication files and utilities

* Configuration of maximum requests, minimum and maximum servers and clients

* Apache 2.x virtual host implementation (with and without dedicated IP addresses)

* Using redirect statements in Apache's configuration files to customise file access

'''The following is a partial list of the used files, terms and utilities:'''

* access logs and error logs

* .htaccess

* httpd.conf

* mod_auth

* htpasswd

* htgroup

* apache2ctl

* httpd

 

====208.2 Apache configuration for HTTPS (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a web server to provide HTTPS.
|}

'''Key Knowledge Areas:'''

* SSL configuration files, tools and utilities

* Ability to generate a server private key and CSR for a commercial CA

* Ability to generate a self-signed Certificate from private CA

* Ability to install the key and Certificate

* Awareness of the issues with Virtual Hosting and use of SSL

* Security issues in SSL use

'''The following is a partial list of the used files, terms and utilities:'''

* Apache2 configuration files

* /etc/ssl/*, /etc/pki/*

* openssl, CA.pl

* SSLEngine, SSLCertificateKeyFile, SSLCertificateFile, SSLCertificateChainFile

* SSLCACertificateFile, SSLCACertificatePath

* SSLProtocol, SSLCipherSuite, ServerTokens, ServerSignature, TraceEnable

 

====208.3 Implementing Squid as a caching proxy (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure a proxy server, including access policies, authentication and resource usage.
|}

'''Key Knowledge Areas:'''

* Squid 3.x configuration files, terms and utilities

* Access restriction methods

* Client user authentication methods

* Layout and content of ACL in the Squid configuration files

'''The following is a partial list of the used files, terms and utilities:'''

* squid.conf

* acl

* http_access

 

====208.4 Implementing Nginx as a web server and a reverse proxy (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure a reverse proxy server, Nginx. Basic configuration of Nginx as a HTTP server is included.
|}

'''Key Knowledge Areas:'''

* Nginx

* Reverse Proxy

* Basic Web Server

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/nginx/

* nginx

 
 

===''Topic 209: File Sharing''===

====209.1 Samba Server Configuration (weight: 5)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 5
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to set up a SAMBA server for various clients. This objective includes setting up Samba for login clients and setting up the workgroup in which a server participates and defining shared directories and printers. Also covered is a configuring a Linux client to use a Samba server. Troubleshooting installations is also tested.
|}

'''Key Knowledge Areas:'''

* Samba version 3 documentation

* Samba configuration files

* Samba tools and utilities

* Mounting Samba shares on Linux

* Samba daemons

* Mapping Windows user names to Linux user names

* User-Level and Share-Level security

'''The following is a partial list of the used files, terms and utilities:'''

* smbd, nmbd

* smbstatus, testparm, smbpasswd, nmblookup

* smbclient

* net

* /etc/smb/*

* /var/log/samba/

 

====209.2 NFS Server Configuration (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to export filesystems using NFS. This objective includes access restrictions, mounting an NFS filesystem on a client and securing NFS.
|}

'''Key Knowledge Areas:'''

* NFS version 3 configuration files

* NFS tools and utilities

* Access restrictions to certain hosts and/or subnets

* Mount options on server and client

* TCP Wrappers

* Awareness of NFSv4

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/exports

* exportfs

* showmount

* nfsstat

* /proc/mounts

* /etc/fstab

* rpcinfo

* mountd

* portmapper

 
 

===''Topic 210: Network Client Management''===

====210.1 DHCP configuration (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a DHCP server. This objective includes setting default and per client options, adding static hosts and BOOTP hosts. Also included is configuring a DHCP relay agent and maintaining the DHCP server.
|}

'''Key Knowledge Areas:'''

* DHCP configuration files, terms and utilities

* Subnet and dynamically-allocated range setup

'''The following is a partial list of the used files, terms and utilities:'''

* dhcpd.conf

* dhcpd.leases

* /var/log/daemon.log and /var/log/messages

* arp

* dhcpd

 

====210.2 PAM authentication (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | The candidate should be able to configure PAM to support authentication using various available methods.
|}

'''Key Knowledge Areas:'''

* PAM configuration files, terms and utilities

* passwd and shadow passwords

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/pam.d

* pam.conf

* nsswitch.conf

* pam_unix, pam_cracklib, pam_limits, pam_listfile

 

====210.3 LDAP client usage (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to perform queries and updates to an LDAP server. Also included is importing and adding items, as well as adding and managing users.
|}

'''Key Knowledge Areas:'''

* LDAP utilities for data management and queries

* Change user passwords

* Querying the LDAP directory

'''The following is a partial list of the used files, terms and utilities:'''

* ldapsearch

* ldappasswd

* ldapadd

* ldapdelete

 

====210.4 Configuring an OpenLDAP server (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a basic OpenLDAP server including knowledge of LDIF format and essential access controls. An understanding of the role of SSSD in authentication and identity management is included.
|}

'''Key Knowledge Areas:'''

* OpenLDAP

* Access Control

* Distinguished Names

* Changetype Operations

* Schemas and Whitepages

* Directories

* Object IDs, Attributes and Classes

* Awareness of System Security Services Daemon (SSSD)

'''The following is a partial list of the used files, terms and utilities:'''

* slapd

* slapd.conf

* LDIF

* slapadd

* slapcat

* slapindex

* /var/lib/ldap/*

* loglevel

 
 

===''Topic 211: E-Mail Services''===

====211.1 Using e-mail servers (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to manage an e-mail server, including the configuration of e-mail aliases, e-mail quotas and virtual e-mail domains. This objective includes configuring internal e-mail relays and monitoring e-mail servers.
|}

'''Key Knowledge Areas:'''

* Configuration files for postfix

* Basic knowledge of the SMTP protocol

* Awareness of sendmail and exim

'''The following is a partial list of the used files, terms and utilities:'''

* Configuration files and commands for postfix

* /etc/postfix/*

* /var/spool/postfix

* sendmail emulation layer commands

* /etc/aliases

* mail-related logs in /var/log/

 

====211.2 Managing Local E-Mail Delivery (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to implement client e-mail management software to filter, sort and monitor incoming user e-mail.
|}

'''Key Knowledge Areas:'''

* procmail configuration files, tools and utilities

* Usage of procmail on both server and client side

'''The following is a partial list of the used files, terms and utilities:'''

* ~/.procmailrc

* /etc/procmailrc

* procmail

* mbox and Maildir formats

 

====211.3 Managing Remote E-Mail Delivery (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure POP and IMAP daemons.
|}

'''Key Knowledge Areas:'''

* Courier IMAP and Courier POP configuration

* Dovecot configuration

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/courier/*

* dovecot.conf

 
 

===''Topic 212: System Security''===

====212.1 Configuring a router (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a system to perform network address translation (NAT, IP masquerading) and state its significance in protecting a network. This objective includes configuring port redirection, managing filter rules and averting attacks.
|}

'''Key Knowledge Areas:'''

* iptables configuration files, tools and utilities

* Tools, commands and utilities to manage routing tables.

* Private address ranges

* Port redirection and IP forwarding

* List and write filtering and rules that accept or block datagrams based on source or destination protocol, port and address

* Save and reload filtering configurations

* Awareness of ip6tables and filtering

'''The following is a partial list of the used files, terms and utilities:'''

* /proc/sys/net/ipv4

* /etc/services

* iptables

 

====212.2 Managing FTP servers (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure an FTP server for anonymous downloads and uploads. This objective includes precautions to be taken if anonymous uploads are permitted and configuring user access.
|}

'''Key Knowledge Areas:'''

* Configuration files, tools and utilities for Pure-FTPd and vsftpd

* Awareness of ProFTPd

* Understanding of passive vs. active FTP connections

'''The following is a partial list of the used files, terms and utilities:'''

* vsftpd.conf

* important Pure-FTPd command line options

 

====212.3 Secure shell (SSH) (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure and secure an SSH daemon. This objective includes managing keys and configuring SSH for users. Candidates should also be able to forward an application protocol over SSH and manage the SSH login.
|}

'''Key Knowledge Areas:'''

* OpenSSH configuration files, tools and utilities

* Login restrictions for the superuser and the normal users

* Managing and using server and client keys to login with and without password

* Usage of multiple connections from multiple hosts to guard against loss of connection to remote host following configuration changes

'''The following is a partial list of the used files, terms and utilities:'''

* ssh

* sshd

* /etc/ssh/sshd_config

* /etc/ssh/*

* Private and public key files

* PermitRootLogin, PubKeyAuthentication, AllowUsers, PasswordAuthentication, Protocol

 

====212.4 Security tasks (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to receive security alerts from various sources, install, configure and run intrusion detection systems and apply security patches and bugfixes.
|}

'''Key Knowledge Areas:'''

* Tools and utilities to scan and test ports on a server

* Locations and organisations that report security alerts as Bugtraq, CERT, CIAC or other sources

* Tools and utilities to implement an intrusion detection system (IDS)

* Awareness of OpenVAS and Snort

'''The following is a partial list of the used files, terms and utilities:'''

* telnet

* nmap

* fail2ban

* nc

* iptables

 

====212.5 OpenVPN (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a VPN (Virtual Private Network) and create secure point-to-point or site-to-site connections.
|}

'''Key Knowledge Areas:'''

* OpenVPN

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/openvpn/*

* openvpn

 
 

==Future Change Considerations==

Future changes to the objective will/may include:

* EFI shell, gdisk, parted not included. More appropriate in LPIC-1 update.

* lighttpd would have been too much coverage of web services. Perhaps reduce Apache next revision to make room.

* host level IDS (tripwire, AIDE, etc) to be covered in future LPIC-1.

* sieve and maildrop to be considered in a future update.

* SAN, AoE, and FCoE to be considered in a future update.

* encrypted file systems are covered in-depth in LPI-303 exam.

LPIC-2 Objectives V4

2013-06-11T21:44:57Z

StarnixAdmin: /* Introduction */

__FORCETOC__
==Introduction==

This is a required exam for LPI certification Level 2. It covers advanced skills for the Linux professional that are common across all distributions of Linux.

Overview of Tasks

To pass LPIC-2, the candidate should be able to:

* Administer a small to medium-sized site
* Plan, implement, maintain, keep consistent, secure, and troubleshoot a small mixed (MS, Linux) network, including a:
** LAN server (Samba, NFS, DNS, DHCP, client management)
** Internet Gateway (firewall, VPN, SSH, web cache/proxy, mail)
** Internet Server (web server and reverse proxy, FTP server)
* Supervise assistants
* Advise management on automation and purchases

 

==Version Information==

These objectives are version 4.0.0. This version is to go live on Oct 1, 2013.

This is also a [[LPIC2SummaryVersion3To4|summary and detailed information]] on the changes from version 3.5.x to 4.0.0 of the objectives.

The [[LPIC-2_Objectives_V3|version 3.x of the LPIC-2 Objectives]] are still online.
 

==Addenda==

===''Version Update (Oct 1st, 2013)''===

* updated to version 4.0.0

 

==Translations of Objectives==

The following translations of the objectives are available on this wiki:

* [[LPIC-2_Objectives|English]]

* [[LPIC-2_Objectives(ES)|Spanish]]

* [[LPIC-2_Objectives(RU)|Russian]]

* [[LPIC-2_Objectives(Greek)|Greek]]

* [[LPIC-2_Objectives(Turkish)|Turkish]]

* [[LPIC-2_Objectives(FR)|French]]

 

==Objectives: Exam 201==

===''Topic 200: Capacity Planning''===

====200.1 Measure Resource Usage (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Candidates should be able to measure hardware resource and network bandwidth usage.

|}

'''Key Knowledge Areas:'''

* Measure CPU usage.

* Measure memory usage.

* Measure disk I/O.

* Measure network I/O.

* Measure firewalling and routing throughput.

* Map client bandwidth usage.

'''The following is a partial list of the used files, terms and utilities:'''

* iostat

* vmstat

* netstat

* pstree, ps

* w

* lsof

* top

* uptime

* sar

 

====200.2 Troubleshoot Resource Problems (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Candidates should be able to identify and troubleshoot resource problems.

|}

'''Key Knowledge Areas:'''

* Match / correlate system symptoms with likely problems.

* Estimate throughput and identify bottlenecks in a system including networking.

'''The following is a partial list of the used files, terms and utilities:'''

* swap

* processes blocked on I/O

* blocks in

* blocks out

* network

 

====200.3 Predict Future Resource Needs (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" |

'''Description'''

| style="background:#eaeaea" |

Candidates should be able to monitor resource usage to predict future resource needs.

|}

'''Key Knowledge Areas:'''

* Use collectd to monitor IT infrastructure usage.

* Predict capacity break point of a configuration.

* Observe growth rate of capacity usage.

* Graph the trend of capacity usage.

* Awareness of monitoring solutions such as Nagios, MRTG and Cacti

'''The following is a partial list of the used files, terms and utilities:'''

* diagnose

* predict growth

* resource exhaustion

 
 

===''Topic 201: Linux Kernel''===

====201.1 Kernel components (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to utilise kernel components that are necessary to specific hardware, hardware drivers, system resources and requirements. This objective includes implementing different types of kernel images, understanding stable and longterm kernels and patches, as well as using kernel modules.
|}

'''Key Knowledge Areas:'''

* Kernel 2.6.x documentation

* Kernel 3.x documentation

'''The following is a partial list of the used files, terms and utilities:'''

* /usr/src/linux

* /usr/src/linux/Documentation

* zImage

* bzImage

 

====201.2 Compiling a Linux kernel (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly configure a kernel to include or disable specific features of the Linux kernel as necessary. This objective includes compiling and recompiling the Linux kernel as needed, updating and noting changes in a new kernel, creating an initrd image and installing new kernels.
|}

'''Key Knowledge Areas:'''

* /usr/src/linux/

* Kernel Makefiles

* Kernel 2.6.x/3.x make targets

* Customize the current kernel configuration.

* Build a new kernel and appropriate kernel modules.

* Install a new kernel and any modules.

* Ensure that the boot manager can locate the new kernel and associated files.

* Module configuration files

* Awareness of dracut

'''The following is a partial list of the used files, terms and utilities:'''

* mkinitrd

* mkinitramfs

* make

* make targets (all, config, xconfig, menuconfig, gconfig, oldconfig, mrproper, zImage, bzImage, modules, modules_install, rpm-pkg, binrpm-pkg, deb-pkg)

* gzip

* bzip2

* module tools

* /usr/src/linux/.config

* /lib/modules/kernel-version/*

* depmod

 

====201.3 Kernel runtime management and troubleshooting (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to manage and/or query a 2.6.x or 3.x kernel and its loadable modules. Candidates should be able to identify and correct common boot and run time issues. Candidates should understand device detection and management using udev. This objective includes troubleshooting udev rules.
|}

'''Key Knowledge Areas:'''

* Use command-line utilities to get information about the currently running kernel and kernel modules.

* Manually load and unload kernel modules.

* Determine when modules can be unloaded.

* Determine what parameters a module accepts.

* Configure the system to load modules by names other than their file name.

* /proc filesystem

* Content of /, /boot , and /lib/modules

* Tools and utilities to analyse information about the available hardware

* udev rules

'''The following is a partial list of the used files, terms and utilities:'''

* /lib/modules/kernel-version/modules.dep

* module configuration files in /etc

* /proc/sys/kernel/

* /sbin/depmod

* /sbin/rmmod

* /sbin/modinfo

* /bin/dmesg

* /sbin/lspci

* /usr/bin/lsdev

* /sbin/lsmod

* /sbin/modprobe

* /sbin/insmod

* /bin/uname

* /usr/bin/lsusb

* /etc/sysctl.conf, /etc/sysctl.d/

* /sbin/sysctl

* udevmonitor

* /etc/udev

 
 

===''Topic 202: System Startup''===

====202.1 Customising SysV-init system startup (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to query and modify the behaviour of system services at various run levels. A thorough understanding of the init structure and boot process is required. This objective includes interacting with run levels.
|}

'''Key Knowledge Areas:'''

* Linux Standard Base Specification (LSB)

* SysV init environment

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/inittab

* /etc/init.d/

* /etc/rc.d/

* chkconfig

* update-rc.d

* init and telinit

 

====202.2 System recovery (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly manipulate a Linux system during both the boot process and during recovery mode. This objective includes using both the init utility and init-related kernel options. Candidates should be able to determine the cause of errors in loading and usage of bootloaders. GRUB version 2 and GRUB Legacy are the bootloaders of interest.
|}

'''Key Knowledge Areas:'''

* GRUB version 2 and Legacy

* grub shell

* boot loader start and hand off to kernel

* kernel loading

* hardware initialisation and setup

* daemon/service initialisation and setup

* Know the different boot loader install locations on a hard disk or removable device

* Overwriting standard boot loader options and using boot loader shells

* Awareness of UEFI

'''The following is a partial list of the used files, terms and utilities:'''

* mount

* fsck

* inittab, telinit and init with SysV init

* The contents of /boot/ and /boot/grub/

* GRUB

* grub-install

* initrd, initramfs

* Master boot record

 

====202.3 Alternate Bootloaders (weight: 1)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be aware of other bootloaders and their major features.
|}

'''Key Knowledge Areas:'''

* LILO

* SYSLINUX, ISOLINUX, PXELINUX

* Understanding of PXE

'''The following is a partial list of the used files, terms and utilities:'''

* lilo, /etc/lilo.conf

* syslinux

* extlinux

* isolinux.bin

* isolinux.cfg

* pxelinux.0

* pxelinux.cfg/*

 
 

===''Topic 203: Filesystem and Devices''===

====203.1 Operating the Linux filesystem (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly configure and navigate the standard Linux filesystem. This objective includes configuring and mounting various filesystem types.
|}

'''Key Knowledge Areas:'''

* The concept of the fstab configuration

* Tools and utilities for handling SWAP partitions and files

* Use of UUIDs for identifying and mounting file systems

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/fstab

* /etc/mtab

* /proc/mounts

* mount and umount

* blkid

* sync

* swapon

* swapoff

 

====203.2 Maintaining a Linux filesystem (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to properly maintain a Linux filesystem using system utilities. This objective includes manipulating standard filesystems and monitoring SMART devices.
|}

'''Key Knowledge Areas:'''

* Tools and utilities to manipulate and ext2, ext3 and ext4

* Tools and utilities to manipulate xfs

* Awareness of Btrfs

'''The following is a partial list of the used files, terms and utilities:'''

* fsck (fsck.*)

* mkfs (mkfs.*)

* dumpe2fs, xfsdump, xfsrestore

* debugfs

* tune2fs

* mkswap

* xfs_info, xfs_check and xfs_repair

* smartd, smartctl

 

====203.3 Creating and configuring filesystem options (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure automount filesystems using AutoFS. This objective includes configuring automount for network and device filesystems. Also included is creating filesystems for devices such as CD-ROMs and a basic feature knowledge of encrypted filesystems.
|}

'''Key Knowledge Areas:'''

* autofs configuration files

* UDF and ISO9660 tools and utilities

* awareness of CD-ROM filesystems (UDF, ISO9660, HFS)

* awareness of CD-ROM filesystem extensions (Joliet, Rock Ridge, El Torito)

* basic feature knowledge of encrypted filesystems

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/auto.master

* /etc/auto.[dir]

* mkisofs

 
 

===''Topic 204: Advanced Storage Device Administration''===

====204.1 Configuring RAID (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure and implement software RAID. This objective includes using and configuring RAID 0, 1 and 5.
|}

'''Key Knowledge Areas:'''

* Software RAID configuration files and utilities

'''The following is a partial list of the used files, terms and utilities:'''

* mdadm.conf

* mdadm

* /proc/mdstat

* partition type 0xFD

 

====204.2 Adjusting Storage Device Access (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure kernel options to support various drives. This objective includes software tools to view & modify hard disk settings including iSCSI devices.
|}

'''Key Knowledge Areas:'''

* Tools and utilities to configure DMA for IDE devices including ATAPI and SATA

* Tools and utilities to manipulate or analyse system resources (e.g. interrupts)

* Awareness of sdparm command and its uses

* Tools and utilities for iSCSI

'''The following is a partial list of the used files, terms and utilities:'''

* hdparm, sdparm

* tune2fs

* sysctl

* /dev/hd* & /dev/sd*

* iscsiadm, iscsid and iscsid.conf

* WWNN, WWPN, WWN, LUN numbers
 

====204.3 Logical Volume Manager (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to create and remove logical volumes, volume groups, and physical volumes. This objective includes snapshots and resizing logical volumes.
|}

'''Key Knowledge Areas:'''

* Tools in the LVM suite

* Resizing, renaming, creating, and removing logical volumes, volume groups, and physical volumes

* Creating and maintaining snapshots

* Activating volume groups

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/pv*

* /sbin/lv*

* /sbin/vg*

* mount

* /dev/mapper/

 
 

===''Topic 205: Networking Configuration''===

====205.1 Basic networking configuration (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a network device to be able to connect to a local, wired or wireless, and a wide-area network. This objective includes being able to communicate between various subnets within a single network including both IPv4 and IPv6 networks.
|}

'''Key Knowledge Areas:'''

* Utilities to configure and manipulate ethernet network interfaces

* Configuring wireless networks

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/route

* /sbin/ifconfig

* /sbin/ip

* /usr/sbin/arp

* /sbin/iwconfig

* /sbin/iwlist

 

====205.2 Advanced Network Configuration (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a network device to implement various network authentication schemes. This objective includes configuring a multi-homed network device and resolving communication problems.
|}

'''Key Knowledge Areas:'''

* Utilities to manipulate routing tables

* Utilities to configure and manipulate ethernet network interfaces

* Utilities to analyse the status of the network devices

* Utilities to monitor and analyse the TCP/IP traffic

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/route

* /sbin/ifconfig

* /bin/netstat

* /bin/ping

* /usr/sbin/arp

* /usr/sbin/tcpdump

* /usr/sbin/lsof

* /usr/bin/nc

* /sbin/ip

* nmap

 

====205.3 Troubleshooting network issues (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to identify and correct common network setup issues, to include knowledge of locations for basic configuration files and commands.
|}

'''Key Knowledge Areas:'''

* Location and content of access restriction files

* Utilities to configure and manipulate ethernet network interfaces

* Utilities to manage routing tables

* Utilities to list network states.

* Utilities to gain information about the network configuration

* Methods of information about the recognised and used hardware devices

* System initialisation files and their contents (SysV init process)

* Awareness of NetworkManager and its impact on network configuration

'''The following is a partial list of the used files, terms and utilities:'''

* /sbin/ifconfig

* /sbin/route

* /bin/netstat

* /etc/network || /etc/sysconfig/network-scripts/

* System log files such as /var/log/syslog & /var/log/messages

* /bin/ping

* /etc/resolv.conf

* /etc/hosts

* /etc/hostname | /etc/HOSTNAME

* /bin/hostname

* /usr/sbin/traceroute

* /bin/dmesg

* /etc/hosts.allow, /etc/hosts.deny

 
 

===''Topic 206: System Maintenance''===

====206.1 Make and install programs from source (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to build and install an executable program from source. This objective includes being able to unpack a file of sources.
|}

'''Key Knowledge Areas:'''

* Unpack source code using common compression and archive utilities.

* Understand basics of invoking make to compile programs.

* Apply parameters to a configure script.

* Know where sources are stored by default.

'''The following is a partial list of the used files, terms and utilities:'''

* /usr/src/

* gunzip

* gzip

* bzip2

* tar

* configure

* make

* uname

* install

* patch

 

====206.2 Backup operations (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to use system tools to back up important system data.
|}

'''Key Knowledge Areas:'''

* Knowledge about directories that have to be include in backups

* Awareness of network backup solutions such as Amanda, Bacula and BackupPC

* Knowledge of the benefits and drawbacks of tapes, CDR, disk or other backup media

* Perform partial and manual backups.

* Verify the integrity of backup files.

* Partially or fully restore backups.

'''The following is a partial list of the used files, terms and utilities:'''

* /bin/sh

* dd

* tar

* /dev/st* and /dev/nst*

* mt

* rsync

 

====206.3 Notify users on system-related issues (weight: 1)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to notify the users about current issues related to the system.
|}

'''Key Knowledge Areas:'''

* Automate communication with users through logon messages.

* Inform active users of system maintenance

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/issue

* /etc/issue.net

* /etc/motd

* wall

* /sbin/shutdown

 
 

==Objectives: Exam 202==

===''Topic 207: Domain Name Server''===

====207.1 Basic DNS server configuration (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure BIND to function as a caching-only DNS server. This objective includes the ability to convert older BIND configuration files to newer format, managing a running server and configuring logging.
|}

'''Key Knowledge Areas:'''

* BIND 9.x configuration files, terms and utilities

* Defining the location of the BIND zone files in BIND configuration files

* Reloading modified configuration and zone files

* Awareness of dnsmasq, djbdns and PowerDNS as alternate name servers

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/named.conf

* /var/named/*

* /usr/sbin/rndc

* kill

* host

* dig

 

====207.2 Create and maintain DNS zones (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to create a zone file for a forward or reverse zone or root level server. This objective includes setting appropriate values for records, adding hosts in zones and adding zones to the DNS. A candidate should also be able to delegate zones to another DNS server.
|}

'''Key Knowledge Areas:'''

* BIND 9 configuration files, terms and utilities

* Utilities to request information from the DNS server

* Layout, content and file location of the BIND zone files

* Various methods to add a new host in the zone files, including reverse zones

'''The following is a partial list of the used files, terms and utilities:'''

* /var/named/*

* zone file syntax

* resource record formats

* dig

* nslookup

* host

 

====207.3 Securing a DNS server (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a DNS server to run as a non-root user and run in a chroot jail. This objective includes secure exchange of data between DNS servers.
|}

'''Key Knowledge Areas:'''

* BIND 9 configuration files

* Configuring BIND to run in a chroot jail

* Split configuration of BIND using the forwarders statement

* Configuring and using transaction signatures (TSIG)

* Awareness of DNSSEC and basic tools

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/named.conf

* /etc/passwd

* DNSSEC

* dnssec-keygen

* dnssec-signzone

 
 

===''Topic 208: Web Services''===

====208.1 Basic Apache configuration (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure a web server. This objective includes monitoring the server's load and performance, restricting client user access, configuring support for scripting languages as modules and setting up client user authentication. Also included is configuring server options to restrict usage of resources. Candidates should be able to configure a web server to use virtual hosts and customise file access.
|}

'''Key Knowledge Areas:'''

* Apache 2.x configuration files, terms and utilities

* Apache log files configuration and content

* Access restriction methods and files

* mod_perl and PHP configuration

* Client user authentication files and utilities

* Configuration of maximum requests, minimum and maximum servers and clients

* Apache 2.x virtual host implementation (with and without dedicated IP addresses)

* Using redirect statements in Apache's configuration files to customise file access

'''The following is a partial list of the used files, terms and utilities:'''

* access logs and error logs

* .htaccess

* httpd.conf

* mod_auth

* htpasswd

* htgroup

* apache2ctl

* httpd

 

====208.2 Apache configuration for HTTPS (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a web server to provide HTTPS.
|}

'''Key Knowledge Areas:'''

* SSL configuration files, tools and utilities

* Ability to generate a server private key and CSR for a commercial CA

* Ability to generate a self-signed Certificate from private CA

* Ability to install the key and Certificate

* Awareness of the issues with Virtual Hosting and use of SSL

* Security issues in SSL use

'''The following is a partial list of the used files, terms and utilities:'''

* Apache2 configuration files

* /etc/ssl/*, /etc/pki/*

* openssl, CA.pl

* SSLEngine, SSLCertificateKeyFile, SSLCertificateFile, SSLCertificateChainFile

* SSLCACertificateFile, SSLCACertificatePath

* SSLProtocol, SSLCipherSuite, ServerTokens, ServerSignature, TraceEnable

 

====208.3 Implementing Squid as a caching proxy (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure a proxy server, including access policies, authentication and resource usage.
|}

'''Key Knowledge Areas:'''

* Squid 3.x configuration files, terms and utilities

* Access restriction methods

* Client user authentication methods

* Layout and content of ACL in the Squid configuration files

'''The following is a partial list of the used files, terms and utilities:'''

* squid.conf

* acl

* http_access

 

====208.4 Implementing Nginx as a web server and a reverse proxy (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure a reverse proxy server, Nginx. Basic configuration of Nginx as a HTTP server is included.
|}

'''Key Knowledge Areas:'''

* Nginx

* Reverse Proxy

* Basic Web Server

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/nginx/

* nginx

 
 

===''Topic 209: File Sharing''===

====209.1 Samba Server Configuration (weight: 5)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 5
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to set up a SAMBA server for various clients. This objective includes setting up Samba for login clients and setting up the workgroup in which a server participates and defining shared directories and printers. Also covered is a configuring a Linux client to use a Samba server. Troubleshooting installations is also tested.
|}

'''Key Knowledge Areas:'''

* Samba version 3 documentation

* Samba configuration files

* Samba tools and utilities

* Mounting Samba shares on Linux

* Samba daemons

* Mapping Windows user names to Linux user names

* User-Level and Share-Level security

'''The following is a partial list of the used files, terms and utilities:'''

* smbd, nmbd

* smbstatus, testparm, smbpasswd, nmblookup

* smbclient

* net

* /etc/smb/*

* /var/log/samba/

 

====209.2 NFS Server Configuration (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to export filesystems using NFS. This objective includes access restrictions, mounting an NFS filesystem on a client and securing NFS.
|}

'''Key Knowledge Areas:'''

* NFS version 3 configuration files

* NFS tools and utilities

* Access restrictions to certain hosts and/or subnets

* Mount options on server and client

* TCP Wrappers

* Awareness of NFSv4

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/exports

* exportfs

* showmount

* nfsstat

* /proc/mounts

* /etc/fstab

* rpcinfo

* mountd

* portmapper

 
 

===''Topic 210: Network Client Management''===

====210.1 DHCP configuration (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a DHCP server. This objective includes setting default and per client options, adding static hosts and BOOTP hosts. Also included is configuring a DHCP relay agent and maintaining the DHCP server.
|}

'''Key Knowledge Areas:'''

* DHCP configuration files, terms and utilities

* Subnet and dynamically-allocated range setup

'''The following is a partial list of the used files, terms and utilities:'''

* dhcpd.conf

* dhcpd.leases

* /var/log/daemon.log and /var/log/messages

* arp

* dhcpd

 

====210.2 PAM authentication (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | The candidate should be able to configure PAM to support authentication using various available methods.
|}

'''Key Knowledge Areas:'''

* PAM configuration files, terms and utilities

* passwd and shadow passwords

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/pam.d

* pam.conf

* nsswitch.conf

* pam_unix, pam_cracklib, pam_limits, pam_listfile

 

====210.3 LDAP client usage (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to perform queries and updates to an LDAP server. Also included is importing and adding items, as well as adding and managing users.
|}

'''Key Knowledge Areas:'''

* LDAP utilities for data management and queries

* Change user passwords

* Querying the LDAP directory

'''The following is a partial list of the used files, terms and utilities:'''

* ldapsearch

* ldappasswd

* ldapadd

* ldapdelete

 

====210.4 Configuring an OpenLDAP server (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a basic OpenLDAP server including knowledge of LDIF format and essential access controls. An understanding of the role of SSSD in authentication and identity management is included.
|}

'''Key Knowledge Areas:'''

* OpenLDAP

* Access Control

* Distinguished Names

* Changetype Operations

* Schemas and Whitepages

* Directories

* Object IDs, Attributes and Classes

* Awareness of System Security Services Daemon (SSSD)

'''The following is a partial list of the used files, terms and utilities:'''

* slapd

* slapd.conf

* LDIF

* slapadd

* slapcat

* slapindex

* /var/lib/ldap/*

* loglevel

 
 

===''Topic 211: E-Mail Services''===

====211.1 Using e-mail servers (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to manage an e-mail server, including the configuration of e-mail aliases, e-mail quotas and virtual e-mail domains. This objective includes configuring internal e-mail relays and monitoring e-mail servers.
|}

'''Key Knowledge Areas:'''

* Configuration files for postfix

* Basic knowledge of the SMTP protocol

* Awareness of sendmail and exim

'''The following is a partial list of the used files, terms and utilities:'''

* Configuration files and commands for postfix

* /etc/postfix/*

* /var/spool/postfix

* sendmail emulation layer commands

* /etc/aliases

* mail-related logs in /var/log/

 

====211.2 Managing Local E-Mail Delivery (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to implement client e-mail management software to filter, sort and monitor incoming user e-mail.
|}

'''Key Knowledge Areas:'''

* procmail configuration files, tools and utilities

* Usage of procmail on both server and client side

'''The following is a partial list of the used files, terms and utilities:'''

* ~/.procmailrc

* /etc/procmailrc

* procmail

* mbox and Maildir formats

 

====211.3 Managing Remote E-Mail Delivery (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to install and configure POP and IMAP daemons.
|}

'''Key Knowledge Areas:'''

* Courier IMAP and Courier POP configuration

* Dovecot configuration

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/courier/*

* dovecot.conf

 
 

===''Topic 212: System Security''===

====212.1 Configuring a router (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a system to perform network address translation (NAT, IP masquerading) and state its significance in protecting a network. This objective includes configuring port redirection, managing filter rules and averting attacks.
|}

'''Key Knowledge Areas:'''

* iptables configuration files, tools and utilities

* Tools, commands and utilities to manage routing tables.

* Private address ranges

* Port redirection and IP forwarding

* List and write filtering and rules that accept or block datagrams based on source or destination protocol, port and address

* Save and reload filtering configurations

* Awareness of ip6tables and filtering

'''The following is a partial list of the used files, terms and utilities:'''

* /proc/sys/net/ipv4

* /etc/services

* iptables

 

====212.2 Managing FTP servers (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure an FTP server for anonymous downloads and uploads. This objective includes precautions to be taken if anonymous uploads are permitted and configuring user access.
|}

'''Key Knowledge Areas:'''

* Configuration files, tools and utilities for Pure-FTPd and vsftpd

* Awareness of ProFTPd

* Understanding of passive vs. active FTP connections

'''The following is a partial list of the used files, terms and utilities:'''

* vsftpd.conf

* important Pure-FTPd command line options

 

====212.3 Secure shell (SSH) (weight: 4)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 4
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure and secure an SSH daemon. This objective includes managing keys and configuring SSH for users. Candidates should also be able to forward an application protocol over SSH and manage the SSH login.
|}

'''Key Knowledge Areas:'''

* OpenSSH configuration files, tools and utilities

* Login restrictions for the superuser and the normal users

* Managing and using server and client keys to login with and without password

* Usage of multiple connections from multiple hosts to guard against loss of connection to remote host following configuration changes

'''The following is a partial list of the used files, terms and utilities:'''

* ssh

* sshd

* /etc/ssh/sshd_config

* /etc/ssh/*

* Private and public key files

* PermitRootLogin, PubKeyAuthentication, AllowUsers, PasswordAuthentication, Protocol

 

====212.4 Security tasks (weight: 3)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to receive security alerts from various sources, install, configure and run intrusion detection systems and apply security patches and bugfixes.
|}

'''Key Knowledge Areas:'''

* Tools and utilities to scan and test ports on a server

* Locations and organisations that report security alerts as Bugtraq, CERT, CIAC or other sources

* Tools and utilities to implement an intrusion detection system (IDS)

* Awareness of OpenVAS and Snort

'''The following is a partial list of the used files, terms and utilities:'''

* telnet

* nmap

* fail2ban

* nc

* iptables

 

====212.5 OpenVPN (weight: 2)====

{|
| style="background:#dadada" |

'''Weight'''

| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''

| style="background:#eaeaea" | Candidates should be able to configure a VPN (Virtual Private Network) and create secure point-to-point or site-to-site connections.
|}

'''Key Knowledge Areas:'''

* OpenVPN

'''The following is a partial list of the used files, terms and utilities:'''

* /etc/openvpn/*

* openvpn

 
 

==Future Change Considerations==

Future changes to the objective will/may include:

* EFI shell, gdisk, parted not included. More appropriate in LPIC-1 update.

* lighttpd would have been too much coverage of web services. Perhaps reduce Apache next revision to make room.

* host level IDS (tripwire, AIDE, etc) to be covered in future LPIC-1.

* sieve and maildrop to be considered in a future update.

* SAN, AoE, and FCoE to be considered in a future update.

* encrypted file systems are covered in-depth in LPI-303 exam.

ObjectiveMaintenanceSchedule

2013-06-11T21:15:51Z

StarnixAdmin: /* Current Objective Schedule */

__FORCETOC__
==Introduction==

Exam objectives are numbered in the format <major>.<minor>.<patch> (eg. version 3.0.4) which parallel the different life cycles used to maintain them.

The 3 different life cycles during maintenance and creation. They are:

* addendum
* revision
* redo

===Relationship with Exam Form Versions===

Exam versions are 'numbered' as <redo><revision><refresh><formID>.

The refresh number starts with 0 (zero) on the first batch of new exam forms for a particular <redo><revision> combination. The refresh number increases by one for each new batch of exam forms.

Example: The first batch of exam forms for the 3.5.x version of the LPIC-1 objectives will be version 350A, 350B, etc.
The second batch of exam forms for this version of the objectives will be 351A, 351B, etc.

==Life Cycles==

===Addendum Life Cycle===

* Period: quarterly (or as required)
* Announcement Schedule: none
* Interested Parties: authors and courseware developers
* Version Impact: updates the patch number

As exam candidates and courseware creators ask for clarification on the objectives, LPI published quarterly updates to the published objectives.

These addenda, if any, are published on a quarterly basis and have no impact on the exam contents.

===Revision Life Cycle===

* Period: 2.5 years
* Announcement Schedule:
** Final Version: 6 months prior to adoption
* Interested Parties: authors, courseware developers
* Version Impact: updates the minor version number

Every 2.5 years, LPI makes revisions to the published objectives. There is no substantial change to the objectives. Instead, versions of covered technologies may change, some technologies may also be dropped. Very rarely will anything be added.

===Republish Life Cycle===

* Period: 5 years (or as required)
* Announcement Schedule:
** Community Feedback Version: 1 year prior to adoption
** Final Version: 6 months prior to adoption
* Interested Parties: everyone
* Version Impact: updates the major version number

Every 5 years, or as required (both sooner or later), LPI will fully update the exam published exam objectives. Almost anything can change (but doesn't), new technologies may be introduced or removed and a full Job Task Analysis is performed to identify new job tasks, technologies and reapportion the weighting of the objectives in the exam.

==Current Objective Schedule==

{| border="1" cellpadding="3"
! Certification
! Current Version
! Live Date
! 2.5yr Refresh
! Full 5yr Republish
! Future 2.5yr Refresh
! Future Full 5yr Republish
|-
| LPIC-1 || 3.5.0 || '''2009-04-01''' || '''2012-04-01''' || 2013-10-01 || 2017-04-01 || 2019-04-01
|-
| LPIC-2 || 3.5.0 || '''2009-07-01''' || '''2012-07-01''' || '''2013-10-01''' || 2016-04-01 || 2018-10-01
|-
| LPIC-300 || 1.0.0 || '''2013-10-01''' || '''2016-04-01''' || 2018-10-01 || ||
|-
| LPIC-301 || 1.0.1 || '''2007-01-01''' || '''2009-06-01''' || End of Lifed || ||
|-
| LPIC-302 || 1.0.0 || '''2007-01-01''' || '''2009-06-01''' || End of Lifed || ||
|-
| LPIC-303 || 1.0.0 || '''2009-01-01''' || '''2011-06-01''' || 2013-06-01 || 2016-06-01 || 2019-01-01
|-
| LPIC-304 || 1.0.0 || '''2010-04-01''' || '''2012-10-01''' || 2014-10-01 || 2017-10-01 || 2020-04-01
|}

'''Dates are approximate unless bold'''

ObjectiveMaintenanceSchedule

2013-06-11T21:15:14Z

StarnixAdmin: /* Current Objective Schedule */

ObjectiveMaintenanceSchedule

2013-06-11T21:13:14Z

StarnixAdmin: /* Current Objective Schedule */

__FORCETOC__
==Introduction==

Exam objectives are numbered in the format <major>.<minor>.<patch> (eg. version 3.0.4) which parallel the different life cycles used to maintain them.

The 3 different life cycles during maintenance and creation. They are:

* addendum
* revision
* redo

===Relationship with Exam Form Versions===

Exam versions are 'numbered' as <redo><revision><refresh><formID>.

The refresh number starts with 0 (zero) on the first batch of new exam forms for a particular <redo><revision> combination. The refresh number increases by one for each new batch of exam forms.

Example: The first batch of exam forms for the 3.5.x version of the LPIC-1 objectives will be version 350A, 350B, etc.
The second batch of exam forms for this version of the objectives will be 351A, 351B, etc.

==Life Cycles==

===Addendum Life Cycle===

* Period: quarterly (or as required)
* Announcement Schedule: none
* Interested Parties: authors and courseware developers
* Version Impact: updates the patch number

As exam candidates and courseware creators ask for clarification on the objectives, LPI published quarterly updates to the published objectives.

These addenda, if any, are published on a quarterly basis and have no impact on the exam contents.

===Revision Life Cycle===

* Period: 2.5 years
* Announcement Schedule:
** Final Version: 6 months prior to adoption
* Interested Parties: authors, courseware developers
* Version Impact: updates the minor version number

Every 2.5 years, LPI makes revisions to the published objectives. There is no substantial change to the objectives. Instead, versions of covered technologies may change, some technologies may also be dropped. Very rarely will anything be added.

===Republish Life Cycle===

* Period: 5 years (or as required)
* Announcement Schedule:
** Community Feedback Version: 1 year prior to adoption
** Final Version: 6 months prior to adoption
* Interested Parties: everyone
* Version Impact: updates the major version number

Every 5 years, or as required (both sooner or later), LPI will fully update the exam published exam objectives. Almost anything can change (but doesn't), new technologies may be introduced or removed and a full Job Task Analysis is performed to identify new job tasks, technologies and reapportion the weighting of the objectives in the exam.

==Current Objective Schedule==

{| border="1" cellpadding="3"
! Certification
! Current Version
! Live Date
! 2.5yr Refresh
! Full 5yr Republish
! Future 2.5yr Refresh
! Future Full 5yr Republish
|-
| LPIC-1 || 3.5.0 || '''2009-04-01''' || '''2012-04-01''' || 2013-10-01 || 2017-04-01 || 2019-04-01
|-
| LPIC-2 || 3.5.0 || '''2009-07-01''' || '''2012-07-01''' || '''2013-10-01''' || 2016-04-01 || 2018-10-01
|-
| LPIC-300 || 1.0.0 || '''2013-10-01''' || '''2009-06-01''' || 2011-06-01 || 2014-06-01 || 2017-01-01
|-
| LPIC-301 || 1.0.1 || '''2007-01-01''' || '''2009-06-01''' || 2011-06-01 || 2014-06-01 || 2017-01-01
|-
| LPIC-302 || 1.0.0 || '''2007-01-01''' || '''2009-06-01''' || 2011-06-01 || 2014-06-01 || 2017-01-01
|-
| LPIC-303 || 1.0.0 || '''2009-01-01''' || '''2011-06-01''' || 2013-06-01 || 2016-06-01 || 2019-01-01
|-
| LPIC-304 || 1.0.0 || '''2010-04-01''' || '''2012-10-01''' || 2014-10-01 || 2017-10-01 || 2020-04-01
|}

'''Dates are approximate unless bold'''
An objective refresh is a non-JTAed reassessment of the current objectives.
An objective reassessment is a full JTAed reassessment of the certification, MQC, and objectives

ObjectiveMaintenanceSchedule

2013-06-11T21:12:22Z

StarnixAdmin: /* Current Objective Schedule */

__FORCETOC__
==Introduction==

Exam objectives are numbered in the format <major>.<minor>.<patch> (eg. version 3.0.4) which parallel the different life cycles used to maintain them.

The 3 different life cycles during maintenance and creation. They are:

* addendum
* revision
* redo

===Relationship with Exam Form Versions===

Exam versions are 'numbered' as <redo><revision><refresh><formID>.

The refresh number starts with 0 (zero) on the first batch of new exam forms for a particular <redo><revision> combination. The refresh number increases by one for each new batch of exam forms.

Example: The first batch of exam forms for the 3.5.x version of the LPIC-1 objectives will be version 350A, 350B, etc.
The second batch of exam forms for this version of the objectives will be 351A, 351B, etc.

==Life Cycles==

===Addendum Life Cycle===

* Period: quarterly (or as required)
* Announcement Schedule: none
* Interested Parties: authors and courseware developers
* Version Impact: updates the patch number

As exam candidates and courseware creators ask for clarification on the objectives, LPI published quarterly updates to the published objectives.

These addenda, if any, are published on a quarterly basis and have no impact on the exam contents.

===Revision Life Cycle===

* Period: 2.5 years
* Announcement Schedule:
** Final Version: 6 months prior to adoption
* Interested Parties: authors, courseware developers
* Version Impact: updates the minor version number

Every 2.5 years, LPI makes revisions to the published objectives. There is no substantial change to the objectives. Instead, versions of covered technologies may change, some technologies may also be dropped. Very rarely will anything be added.

===Republish Life Cycle===

* Period: 5 years (or as required)
* Announcement Schedule:
** Community Feedback Version: 1 year prior to adoption
** Final Version: 6 months prior to adoption
* Interested Parties: everyone
* Version Impact: updates the major version number

Every 5 years, or as required (both sooner or later), LPI will fully update the exam published exam objectives. Almost anything can change (but doesn't), new technologies may be introduced or removed and a full Job Task Analysis is performed to identify new job tasks, technologies and reapportion the weighting of the objectives in the exam.

==Current Objective Schedule==

{| border="1" cellpadding="3"
! Certification
! Current Version
! Live Date
! 2.5yr Refresh
! Full 5yr Republish
! Future 2.5yr Refresh
! Future Full 5yr Republish
|-
| LPIC-1 || 3.5.0 || '''2009-04-01''' || '''2012-04-01''' || 2013-10-01 || 2017-04-01 || 2019-04-01
|-
| LPIC-2 || 3.5.0 || '''2009-07-01''' || '''2012-07-01''' || 2014-01-01 || 2017-07-01 || 2019-07-01
|-
| LPIC-300 || 1.0.0 || '''2013-10-01''' || '''2009-06-01''' || 2011-06-01 || 2014-06-01 || 2017-01-01
|-
| LPIC-301 || 1.0.1 || '''2007-01-01''' || '''2009-06-01''' || 2011-06-01 || 2014-06-01 || 2017-01-01
|-
| LPIC-302 || 1.0.0 || '''2007-01-01''' || '''2009-06-01''' || 2011-06-01 || 2014-06-01 || 2017-01-01
|-
| LPIC-303 || 1.0.0 || '''2009-01-01''' || '''2011-06-01''' || 2013-06-01 || 2016-06-01 || 2019-01-01
|-
| LPIC-304 || 1.0.0 || '''2010-04-01''' || '''2012-10-01''' || 2014-10-01 || 2017-10-01 || 2020-04-01
|}

'''Dates are approximate unless bold'''
An objective refresh is a non-JTAed reassessment of the current objectives.
An objective reassessment is a full JTAed reassessment of the certification, MQC, and objectives

ObjectiveMaintenanceSchedule

2013-06-11T21:12:07Z

StarnixAdmin: /* Current Objective Schedule */

__FORCETOC__
==Introduction==

Exam objectives are numbered in the format <major>.<minor>.<patch> (eg. version 3.0.4) which parallel the different life cycles used to maintain them.

The 3 different life cycles during maintenance and creation. They are:

* addendum
* revision
* redo

===Relationship with Exam Form Versions===

Exam versions are 'numbered' as <redo><revision><refresh><formID>.

The refresh number starts with 0 (zero) on the first batch of new exam forms for a particular <redo><revision> combination. The refresh number increases by one for each new batch of exam forms.

Example: The first batch of exam forms for the 3.5.x version of the LPIC-1 objectives will be version 350A, 350B, etc.
The second batch of exam forms for this version of the objectives will be 351A, 351B, etc.

==Life Cycles==

===Addendum Life Cycle===

* Period: quarterly (or as required)
* Announcement Schedule: none
* Interested Parties: authors and courseware developers
* Version Impact: updates the patch number

As exam candidates and courseware creators ask for clarification on the objectives, LPI published quarterly updates to the published objectives.

These addenda, if any, are published on a quarterly basis and have no impact on the exam contents.

===Revision Life Cycle===

* Period: 2.5 years
* Announcement Schedule:
** Final Version: 6 months prior to adoption
* Interested Parties: authors, courseware developers
* Version Impact: updates the minor version number

Every 2.5 years, LPI makes revisions to the published objectives. There is no substantial change to the objectives. Instead, versions of covered technologies may change, some technologies may also be dropped. Very rarely will anything be added.

===Republish Life Cycle===

* Period: 5 years (or as required)
* Announcement Schedule:
** Community Feedback Version: 1 year prior to adoption
** Final Version: 6 months prior to adoption
* Interested Parties: everyone
* Version Impact: updates the major version number

Every 5 years, or as required (both sooner or later), LPI will fully update the exam published exam objectives. Almost anything can change (but doesn't), new technologies may be introduced or removed and a full Job Task Analysis is performed to identify new job tasks, technologies and reapportion the weighting of the objectives in the exam.

==Current Objective Schedule==

{| border="1" cellpadding="3"
! Certification
! Current Version
! Live Date
! 2.5yr Refresh
! Full 5yr Republish
! Future 2.5yr Refresh
! Future Full 5yr Republish
|-
! !! !! !! Live !! Live !! Live !! Live
|-
| LPIC-1 || 3.5.0 || '''2009-04-01''' || '''2012-04-01''' || 2013-10-01 || 2017-04-01 || 2019-04-01
|-
| LPIC-2 || 3.5.0 || '''2009-07-01''' || '''2012-07-01''' || 2014-01-01 || 2017-07-01 || 2019-07-01
|-
| LPIC-300 || 1.0.0 || '''2013-10-01''' || '''2009-06-01''' || 2011-06-01 || 2014-06-01 || 2017-01-01
|-
| LPIC-301 || 1.0.1 || '''2007-01-01''' || '''2009-06-01''' || 2011-06-01 || 2014-06-01 || 2017-01-01
|-
| LPIC-302 || 1.0.0 || '''2007-01-01''' || '''2009-06-01''' || 2011-06-01 || 2014-06-01 || 2017-01-01
|-
| LPIC-303 || 1.0.0 || '''2009-01-01''' || '''2011-06-01''' || 2013-06-01 || 2016-06-01 || 2019-01-01
|-
| LPIC-304 || 1.0.0 || '''2010-04-01''' || '''2012-10-01''' || 2014-10-01 || 2017-10-01 || 2020-04-01
|}

'''Dates are approximate unless bold'''
An objective refresh is a non-JTAed reassessment of the current objectives.
An objective reassessment is a full JTAed reassessment of the certification, MQC, and objectives

ObjectiveMaintenanceSchedule

2013-06-11T21:08:12Z

StarnixAdmin: /* Current Objective Schedule */

__FORCETOC__
==Introduction==

Exam objectives are numbered in the format <major>.<minor>.<patch> (eg. version 3.0.4) which parallel the different life cycles used to maintain them.

The 3 different life cycles during maintenance and creation. They are:

* addendum
* revision
* redo

===Relationship with Exam Form Versions===

Exam versions are 'numbered' as <redo><revision><refresh><formID>.

The refresh number starts with 0 (zero) on the first batch of new exam forms for a particular <redo><revision> combination. The refresh number increases by one for each new batch of exam forms.

Example: The first batch of exam forms for the 3.5.x version of the LPIC-1 objectives will be version 350A, 350B, etc.
The second batch of exam forms for this version of the objectives will be 351A, 351B, etc.

==Life Cycles==

===Addendum Life Cycle===

* Period: quarterly (or as required)
* Announcement Schedule: none
* Interested Parties: authors and courseware developers
* Version Impact: updates the patch number

As exam candidates and courseware creators ask for clarification on the objectives, LPI published quarterly updates to the published objectives.

These addenda, if any, are published on a quarterly basis and have no impact on the exam contents.

===Revision Life Cycle===

* Period: 2.5 years
* Announcement Schedule:
** Final Version: 6 months prior to adoption
* Interested Parties: authors, courseware developers
* Version Impact: updates the minor version number

Every 2.5 years, LPI makes revisions to the published objectives. There is no substantial change to the objectives. Instead, versions of covered technologies may change, some technologies may also be dropped. Very rarely will anything be added.

===Republish Life Cycle===

* Period: 5 years (or as required)
* Announcement Schedule:
** Community Feedback Version: 1 year prior to adoption
** Final Version: 6 months prior to adoption
* Interested Parties: everyone
* Version Impact: updates the major version number

Every 5 years, or as required (both sooner or later), LPI will fully update the exam published exam objectives. Almost anything can change (but doesn't), new technologies may be introduced or removed and a full Job Task Analysis is performed to identify new job tasks, technologies and reapportion the weighting of the objectives in the exam.

==Current Objective Schedule==

{| border="1" cellpadding="3"
! Certification
! Current Version
! Live Date
! 2.5yr Refresh
! Full 5yr Republish
! Future 2.5yr Refresh
! Future Full 5yr Republish
|-
! !! !! !! Announce !! Live !! Announce !! Live !! Announce !! Live !! Announce !! Live
|-
| LPIC-1 || 3.5.0 || '''2009-04-01''' || '''2011-06-01''' || '''2012-04-01''' || 2013-10-01 || 2014-04-01 || 2016-06-01 || 2017-04-01 || 2018-10-01 || 2019-04-01
|-
| LPIC-2 || 3.5.0 || '''2009-07-01''' || '''2012-01-01''' || '''2012-07-01''' || 2014-01-01 || 2014-07-01 || 2016-09-01 || 2017-07-01 || 2019-01-01 || 2019-07-01
|-
| LPIC-300 || 1.0.1 || '''2013-10-01''' || '''2013-10-01''' || '''2009-06-01''' || 2011-06-01 || 2012-01-01 || 2014-01-01 || 2014-06-01 || 2016-06-01 || 2017-01-01
|-
| LPIC-301 || 1.0.1 || '''2007-01-01''' || '''2009-01-01''' || '''2009-06-01''' || 2011-06-01 || 2012-01-01 || 2014-01-01 || 2014-06-01 || 2016-06-01 || 2017-01-01
|-
| LPIC-302 || 1.0.0 || '''2007-01-01''' || '''2009-01-01''' || '''2009-06-01''' || 2011-06-01 || 2012-01-01 || 2014-01-01 || 2014-06-01 || 2016-06-01 || 2017-01-01
|-
| LPIC-303 || 1.0.0 || '''2009-01-01''' || '''2011-01-01''' || '''2011-06-01''' || 2013-06-01 || 2014-01-01 || 2016-01-01 || 2016-06-01 || 2018-06-01 || 2019-01-01
|-
| LPIC-304 || 1.0.0 || '''2010-04-01''' || '''2012-04-01''' || '''2012-10-01''' || 2014-10-01 || 2015-04-01 || 2017-04-01 || 2017-10-01 || 2019-10-01 || 2020-04-01
|}

'''Dates are approximate unless bold'''
An objective refresh is a non-JTAed reassessment of the current objectives.
An objective reassessment is a full JTAed reassessment of the certification, MQC, and objectives

ObjectiveMaintenanceSchedule

2013-06-11T20:52:20Z

StarnixAdmin: /* Redo Life Cycle */

__FORCETOC__
==Introduction==

Exam objectives are numbered in the format <major>.<minor>.<patch> (eg. version 3.0.4) which parallel the different life cycles used to maintain them.

The 3 different life cycles during maintenance and creation. They are:

* addendum
* revision
* redo

===Relationship with Exam Form Versions===

Exam versions are 'numbered' as <redo><revision><refresh><formID>.

The refresh number starts with 0 (zero) on the first batch of new exam forms for a particular <redo><revision> combination. The refresh number increases by one for each new batch of exam forms.

Example: The first batch of exam forms for the 3.5.x version of the LPIC-1 objectives will be version 350A, 350B, etc.
The second batch of exam forms for this version of the objectives will be 351A, 351B, etc.

==Life Cycles==

===Addendum Life Cycle===

* Period: quarterly (or as required)
* Announcement Schedule: none
* Interested Parties: authors and courseware developers
* Version Impact: updates the patch number

As exam candidates and courseware creators ask for clarification on the objectives, LPI published quarterly updates to the published objectives.

These addenda, if any, are published on a quarterly basis and have no impact on the exam contents.

===Revision Life Cycle===

* Period: 2.5 years
* Announcement Schedule:
** Final Version: 6 months prior to adoption
* Interested Parties: authors, courseware developers
* Version Impact: updates the minor version number

Every 2.5 years, LPI makes revisions to the published objectives. There is no substantial change to the objectives. Instead, versions of covered technologies may change, some technologies may also be dropped. Very rarely will anything be added.

===Republish Life Cycle===

* Period: 5 years (or as required)
* Announcement Schedule:
** Community Feedback Version: 1 year prior to adoption
** Final Version: 6 months prior to adoption
* Interested Parties: everyone
* Version Impact: updates the major version number

Every 5 years, or as required (both sooner or later), LPI will fully update the exam published exam objectives. Almost anything can change (but doesn't), new technologies may be introduced or removed and a full Job Task Analysis is performed to identify new job tasks, technologies and reapportion the weighting of the objectives in the exam.

==Current Objective Schedule==

{| border="1" cellpadding="3"
! Certification
! Current Version
! Live Date
! colspan="2" | 2.5yr Refresh
! colspan="2" | Full 5yr Reassess
! colspan="2" | Future 2.5yr Refresh
! colspan="2" | Future Full 5yr Reassess
|-
! !! !! !! Announce !! Live !! Announce !! Live !! Announce !! Live !! Announce !! Live
|-
| LPIC-1 || 3.0.2 || '''2009-04-01''' || '''2011-06-01''' || '''2012-04-01''' || 2013-10-01 || 2014-04-01 || 2016-06-01 || 2017-04-01 || 2018-10-01 || 2019-04-01
|-
| LPIC-2 || 3.0.5 || '''2009-07-01''' || '''2012-01-01''' || '''2012-07-01''' || 2014-01-01 || 2014-07-01 || 2016-09-01 || 2017-07-01 || 2019-01-01 || 2019-07-01
|-
| LPIC-301 || 1.0.1 || '''2007-01-01''' || '''2009-01-01''' || '''2009-06-01''' || 2011-06-01 || 2012-01-01 || 2014-01-01 || 2014-06-01 || 2016-06-01 || 2017-01-01
|-
| LPIC-302 || 1.0.0 || '''2007-01-01''' || '''2009-01-01''' || '''2009-06-01''' || 2011-06-01 || 2012-01-01 || 2014-01-01 || 2014-06-01 || 2016-06-01 || 2017-01-01
|-
| LPIC-303 || 1.0.0 || '''2009-01-01''' || '''2011-01-01''' || '''2011-06-01''' || 2013-06-01 || 2014-01-01 || 2016-01-01 || 2016-06-01 || 2018-06-01 || 2019-01-01
|-
| LPIC-304 || 1.0.0 || '''2010-04-01''' || '''2012-04-01''' || '''2012-10-01''' || 2014-10-01 || 2015-04-01 || 2017-04-01 || 2017-10-01 || 2019-10-01 || 2020-04-01
|}

'''Dates are approximate unless bold'''
An objective refresh is a non-JTAed reassessment of the current objectives.
An objective reassessment is a full JTAed reassessment of the certification, MQC, and objectives

LPIC-3 300 Objectives

2013-06-11T18:52:18Z

StarnixAdmin: Redirected page to LPIC-3 300 Objectives V1

#REDIRECT [[LPIC-3_300_Objectives_V1]]

LPIC-2 Objectives

2013-06-11T18:50:54Z

StarnixAdmin: Redirected page to LPIC-2 Objectives V4

#REDIRECT [[LPIC-2_Objectives_V4]]

MediaWiki:Sidebar

2013-06-11T18:48:59Z

StarnixAdmin:

MediaWiki:Sidebar

2013-06-11T18:48:45Z

StarnixAdmin:

MediaWiki:Login

2012-11-21T22:06:19Z

StarnixAdmin:

MediaWiki:Login

2012-11-21T22:02:54Z

StarnixAdmin: Created page with "Log in (to create an account, please email webmaster@lpi.org)"

Main Page

2011-11-08T17:03:29Z

StarnixAdmin:

__NOTITLE__
=== Welcome to the Linux Professional Institute wiki! ===

 

This a place for the community to openly discuss everything from exam development topics to LPI policies and procedures.

 

We encourage you to participate in the exam development process by providing your input on our exam objectives. To do so, simply [http://wiki.lpi.org/pubwiki/index.php?title=Special:UserLogin&returnto=Main_Page Create an Account], and then jump in using the navigation bar on the left.

 
We have information on:
* Body of Knowledge Projects
** [[LPIC-2_BoK|LPIC-2 Body of Knowledge]]
* [[LPIC-3|LPIC-3 Certification]]
* [[LPIC-3_305_Objectives|News on the upcoming 305 exam]]

 

You may find the following links useful:

* [http://www.lpi.org/eng/certification/the_lpic_program The Current Published Exam Objectives]
* [http://www.lpi.org/eng/certification/exam_development_process The Exam Development Process]
* [http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev LPI Exam Development Mailing List]
* [http://www.lpi.org/eng/certification/faq LPI's FAQ]
* [http://www.mediawiki.org/wiki/Help:Formatting MediaWiki Markup]
* [[Volunteer Opportunities]]

 

Please contact the [mailto:wiki@lpi.org administrator] with any questions or comments about the wiki, or [mailto:info@lpi.org info@lpi.org] for any inquiries regarding exam development.

MediaWiki:Sidebar

2011-09-07T16:50:10Z

StarnixAdmin:

LinuxEssentials Objectives V1

2011-09-07T16:49:39Z

StarnixAdmin: moved LinuxBasics to LinuxEssentials

__FORCETOC__
==Introduction==
The description of the entire [[LinuxEssentials]] programme is listed [[LinuxEssentials|here]].
 

==Minimally Qualified Candidate Description==
This is a description of a candidate that is just barely
qualified to pass the LPI Introductory Linux exam. This hypothetical
person is called the Minimally Qualified Candidate (MQC). Standards on
the Introductory Linux exam should be set so that this person (and
anyone more able) would pass but anyone less able would not pass.

An LPI Linux and Open Source Technician should
have an understanding of the major components of the Linux operating
system, the technical proficiency to work on the Linux command line and
a basic understanding of security and administration related topics such
as user/group management, working on the command line and permissions.
A LPI Linux ad Open Source Technician is most likely the end user of a mostly managed system.

The LPI Linux and Open Source MQC typically:

* Has a basic understanding of FOSS, the various communities and licenses
* Understands the basic concepts of processes, programs and the components of an Operating System
* Has a rudimentary ability to work on the command line and with files.
* Can use a basic command line editor.
* Has enough network knowledge to get a system up on a LAN.
* Has a basic appreciation of system security, encryption and user/groups and file permissions.

==Version Information==
These objectives are version 0.3.0.
 

==Translations of Objectives==
The following translations of the objectives are available on this wiki:
* [[LinuxBasics|English]]
* [[LinuxBasics(DE)|German]]
 

==Objectives==

===''Topic 1.1: A Career in Open Source and Joining The Linux Community (weight: 7)''===
====1.1.1 Linux Evolution and Popular Operating Systems====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Knowledge of Linux Development and Major Distributions.
|}
'''Key Knowledge Areas:'''
* Open Source Philosophy
* Distributions
* Embedded Systems
'''The following is a partial list of the used files, terms and utilities:'''
* Android
* Debian
* CentOS
 

====1.1.2 Major Open Source Applications====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Awareness of major applications and their uses.
|}
'''Key Knowledge Areas:'''
* Desktop Applications
* Server Applications
* Mobile Applications
* Development Languages
'''The following is a partial list of the used files, terms and utilities:'''
* OpenOffice.org, LibreOffice, Thunderbird, Firefox
* Blender, Gimp, Audacity
* Apache, MySQL, PostgreSQL, Samba, OpenLDAP
* C, Perl, shell, Python, PHP
 

====1.1.3 Understanding "Freeware" and Licensing====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Open Source Communities and Licensing in Free and Commercial Open Source Software.
|}
'''Key Knowledge Areas:'''
* Licensing
'''The following is a partial list of the used files, terms and utilities:'''
* GPL, BSD, Creative Commons
* Free Software, Open Software, FOSS, FLOSS
 

====1.1.4 ICT Skills and Working in Linux====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Basic Information and Communication Technology (ICT) Skills and Working in Linux.
|}
'''Key Knowledge Areas:'''
* Desktop Skills
* Open Source Applications used in an academic setting
'''The following is a partial list of the used files, terms and utilities:'''
* Using a browser, privacy concerns, configuration options, searching the web and saving content
* Cloud Computing
* Password issues
* Use of common open source applications in presentations and projects
 
 

===''Topic 1.2: The Linux Operating System (OS) and Programs (weight: 10)''===
====1.2.1 Using Help Commands and “Man Pages”====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" |Navigation of the various help systems.
|}
'''Key Knowledge Areas:'''
* Man
* Info
'''The following is a partial list of the used files, terms and utilities:'''
* man
* info
* man pages
* whatis
* /usr/share/doc
 

====1.2.2 Choosing an Operating System====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Knowledge of major Linux Operating Systems and how their life cycle is managed.
|}
'''Key Knowledge Areas:'''
* Windows, Mac, Linux differences
'''The following is a partial list of the used files, terms and utilities:'''
* GUI versus command line, desktop configuration
* maintenance cycles, Beta and Stable
 

====1.2.3 Understanding Computer Hardware====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" |Familiarity with the components that go into building desktop and server computers.
|}
'''Key Knowledge Areas:'''
* Hardware
'''The following is a partial list of the used files, terms and utilities:'''
* Hard drives and partitions, motherboards, processors, power supplies, optical drives, peripherals
* display types
* drivers
 

====1.2.4 Where Data is Stored====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Where various types of information are stored on a Linux system.
|}
'''Key Knowledge Areas:'''
* Kernel
* Process
'''The following is a partial list of the used files, terms and utilities:'''
* programs, libraries, packages and package databases, system configuration
* processes and process tables, memory addresses, system messaging and logging
 

====1.2.5 Networking Your Computer====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" |Adding a computer on to a Local Area Network (LAN).
|}
'''Key Knowledge Areas:'''
* internet, network, routers
* Domain Name Service
'''The following is a partial list of the used files, terms and utilities:'''
* route
* resolve.conf
* IPv4, IPv6
* ifconfig, netstat, route
 
 

===''Topic 1.3: The Power of the Command Line (weight: 10)''===
====1.3.1 Using Directories and Listing Files====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Navigation of home and system directories and listing files in various locations.
|}
'''Key Knowledge Areas:'''
* files, directories
'''The following is a partial list of the used files, terms and utilities:'''
* ls, recursive listings, less
* common options for ls
* cd
 

====1.3.2 Creating, Moving and Deleting Files====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Create, move and delete files and directories under the home directory.
|}
'''Key Knowledge Areas:'''
* files, directories
* case sensitivity
'''The following is a partial list of the used files, terms and utilities:'''
* mv, cp, rm, touch
* mkdir, rmdir
 

====1.3.3 Archiving Files on the Command Line====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Archiving files in their home directories.
|}
'''Key Knowledge Areas:'''
* files, directories
* archives, compression
'''The following is a partial list of the used files, terms and utilities:'''
* tar, cpio
* gzip, bzip2
 

====1.3.4 Searching and Extracting Data from Files====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Search and extract data from files in the home directories.
|}
'''Key Knowledge Areas:'''
* Regular Expressions
'''The following is a partial list of the used files, terms and utilities:'''
* grep
* less
 

====1.3.5 Turning Commands into a Script====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 3
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Turning repetitive commands into simple scripts.
|}
'''Key Knowledge Areas:'''
* Bash
'''The following is a partial list of the used files, terms and utilities:'''
* /bin/bash
* arguments
* for loops
 
 

===''Topic 1.4: Keep it Simple: The Text File (weight: 6)''===
====1.4.1 Launch Text Editors like pico or nano====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Launching a simple command line editor.
|}
'''Key Knowledge Areas:'''
* command line text editing
'''The following is a partial list of the used files, terms and utilities:'''
* pico, nano
 

====1.4.2 Editing of Text Files====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Making simple changes to text files.
|}
'''Key Knowledge Areas:'''
* command line text editing
'''The following is a partial list of the used files, terms and utilities:'''
* pico, nano editing functions
 

====1.4.3 Search And Replace of Text====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Finding and replacing simple text in files.
|}
'''Key Knowledge Areas:'''
* command line text editing
'''The following is a partial list of the used files, terms and utilities:'''
* pico, nano search and replace functions
 

====1.4.4 Undo Functions====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Undoing changes in a text file.
|}
'''Key Knowledge Areas:'''
* command line text editing
'''The following is a partial list of the used files, terms and utilities:'''
* pico, nano undo functions
 

====1.4.5 Saving Changes====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Saving changes made to text files in an editor.
|}
'''Key Knowledge Areas:'''
* command line text editing
'''The following is a partial list of the used files, terms and utilities:'''
* pico, nano content saving functions
 
 

===''Topic 1.5: Security and File Permissions (weight: 7)''===
====1.5.1 Basic Security and Identifying User Types====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Various types of users on a Linux system.
|}
'''Key Knowledge Areas:'''
* Root and Un-privileged Users
* System users
'''The following is a partial list of the used files, terms and utilities:'''
* /etc/passwd
* id, who
 

====1.5.2 Creating Users and Groups====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Creating users and groups on a Linux system.
|}
'''Key Knowledge Areas:'''
* user and group commands
* user IDs
'''The following is a partial list of the used files, terms and utilities:'''
* /etc/passwd
* id, lastlog
 

====1.5.3 Setting File Permissions and Ownership====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 2
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Understanding and manipulating file permissions and ownership settings.
|}
'''Key Knowledge Areas:'''
* File permissions and owners
'''The following is a partial list of the used files, terms and utilities:'''
* ls -l
* chmod, chown, chgrp
 

====1.5.4 Special Directories and Files====
{|
| style="background:#dadada" | '''Weight'''
| style="background:#eaeaea" | 1
|-
| style="background:#dadada; padding-right:1em" | '''Description'''
| style="background:#eaeaea" | Special directories and files on a Linux system including special permissions.
|}
'''Key Knowledge Areas:'''
* Hidden files, system files, libraries, repositories,
* /tmp, /var/tmp and special permissions
* File hierarchy
'''The following is a partial list of the used files, terms and utilities:'''
* /etc, /var, /usr
* ls -a, ls -d
 

===''Reference Material''===

===Notes and Comments===

Feel free to add comments here:

# privacy topic?

MediaWiki:Sidebar

2011-08-15T18:39:36Z

StarnixAdmin:

MediaWiki:Sidebar

2011-08-04T03:04:47Z

StarnixAdmin:

Main Page

2010-11-25T16:27:22Z

StarnixAdmin: Changed protection level for "Main Page" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

__NOTITLE__
=== Welcome to the Linux Professional Institute wiki! ===

 

This a place for the community to openly discuss everything from exam development topics to LPI policies and procedures.

 

We encourage you to participate in the exam development process by providing your input on our exam objectives. To do so, simply [http://wiki.lpi.org/pubwiki/index.php?title=Special:UserLogin&returnto=Main_Page Create an Account], and then jump in using the navigation bar on the left.

 
We have information on:
* [[LPIC-3|LPIC-3 Certification]]
* [[LPIC-3_305_Objectives|News on the upcoming 305 exam]]

 

You may find the following links useful:

* [http://www.lpi.org/eng/certification/the_lpic_program The Current Published Exam Objectives]
* [http://www.lpi.org/eng/certification/exam_development_process The Exam Development Process]
* [http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev LPI Exam Development Mailing List]
* [http://www.lpi.org/eng/certification/faq LPI's FAQ]
* [http://www.mediawiki.org/wiki/Help:Formatting MediaWiki Markup]
* [[Volunteer Opportunities]]

 

Please contact the [mailto:wiki@lpi.org administrator] with any questions or comments about the wiki, or [mailto:info@lpi.org info@lpi.org] for any inquiries regarding exam development.

Main Page

2010-11-25T16:26:46Z

StarnixAdmin: Reverted edits by Donaldbanks (Talk) to last revision by GMatthewRice

__NOTITLE__
=== Welcome to the Linux Professional Institute wiki! ===

 

This a place for the community to openly discuss everything from exam development topics to LPI policies and procedures.

 

We encourage you to participate in the exam development process by providing your input on our exam objectives. To do so, simply [http://wiki.lpi.org/pubwiki/index.php?title=Special:UserLogin&returnto=Main_Page Create an Account], and then jump in using the navigation bar on the left.

 
We have information on:
* [[LPIC-3|LPIC-3 Certification]]
* [[LPIC-3_305_Objectives|News on the upcoming 305 exam]]

 

You may find the following links useful:

* [http://www.lpi.org/eng/certification/the_lpic_program The Current Published Exam Objectives]
* [http://www.lpi.org/eng/certification/exam_development_process The Exam Development Process]
* [http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev LPI Exam Development Mailing List]
* [http://www.lpi.org/eng/certification/faq LPI's FAQ]
* [http://www.mediawiki.org/wiki/Help:Formatting MediaWiki Markup]
* [[Volunteer Opportunities]]

 

Please contact the [mailto:wiki@lpi.org administrator] with any questions or comments about the wiki, or [mailto:info@lpi.org info@lpi.org] for any inquiries regarding exam development.

LPIC-305

2010-09-13T15:35:19Z

StarnixAdmin:

__FORCETOC__
==Introduction==
The description of the entire [[LPIC-3]] programme is listed [[LPIC-3|here]].

LPI is just getting underway in the development of the next LPIC-3 Enterprise exam. This exam will cover Mail and Messaging Services.

The main milestones to be achieved are:

# Consult with industry, partners and communities on requirements
# Create draft objectives
# Perform a JTA (Job Task Analysis) survey to determine objective weighting
# Develop exam content (aka exam items)
# Have a 305 Beta exam period for public feedback and testing
# Evaluation JTA and Beta exam results
# Launch final 305 exam

We are commencing this milestone 1 as described above and would like to have the final exam launch in 2011.
 

==How To Add to This Discussion==

Please add to the discussion on the lpi-examdev mailing list:

   http://list.lpi.org/mailman/listinfo/lpi-examdev

This page will be updated as we progress. Alternatively, register on this wiki and add your comments below.

==Topics to Be Considered for Coverage==

This is a brief list of topics under consideration:

Mail Services

* E-mail Concepts and Troubleshooting
* MTA (Postfix and/or Sendmail and/or Exim)
* IMAP/POP services (courier and/or dovecot and/or uw-imap)
* Virus scanning (Amavis)
* Spam filtering (SpamAssasin)
* MUA (Mail User Agents aka e-mail clients)
* Secure POP, IMAP, SMTP (setting up certificates, configuration)
* Integration with LDAP and/or MySQL
* greylisting
* blacklisting and RBLs

Messaging Services

* Messaging Servers (OpenFire and/or Jabberd)
* Messaging clients (Pidgin, Kopete)
* Messaging protocols (XMPP)
* Integration with LDAP and/or MySQL
* IRC clients and servers (maybe)

==The Minimally Qualified Candidate for This Exam==

This is a description of a Linux professional that is just barely
qualified to pass the LPI Level 3 Linux exams. This hypothetical person
is called the Minimally Qualified Candidate (MQC). Standards on the
Level 3 exams should be set so that this person (and anyone more able)
would pass but anyone less able would not pass.

An LPI certified Level 3 Linux professional (designated LPIC-3) should
have the technical capability to perform system administration at the
enterprise level. A [[LPIC-3]] certification holder should be able to understand, plan roll-outs,
install, configure, maintain and troubleshoot the technologies being
tested. These technologies differ for each exam but the level of ability
is at an enterprise level.

The LPIC-3 MQC typically (Yes, some of these bullets are specific to particular exams in the LPIC-3 series):

* Has installed and maintained Linux on a number of computers for various purposes for a number of years.
* Has integration experience with diverse technologies and operating systems.
* Has professional experience as, or training for, an enterprise level Linux professional. (Including having experience as a part of another role.)
* Is comfortable with advanced and enterprise levels of Linux administration including installation, management, security, troubleshooting and maintenance.
* Is able to use opensource tools to measure capacity planning and troubleshooting resource problems.
* Is able create scripts in Bash or Perl or has knowledge of at least one system programming language (such as C).
* Is able to plan, architecture, design, build and implement a full environment using E-mail and Messaging services as well as measure the capacity planning and security of the services.

==Community Comments==

Please add your comments or see above about the lpi-examdev mailing list.

LPIC-305

2010-09-13T15:34:12Z

StarnixAdmin: /* Comments */

__FORCETOC__
==Introduction==
The description of the entire [[LPIC-3]] programme is listed [[LPIC-3|here]].

LPI is just getting underway in the development of the next LPIC-3 Enterprise exam. This exam will cover Mail and Messaging Services.

The main milestones to be achieved are:

# Consult with industry, partners and communities on requirements
# Create draft objectives
# Perform a JTA (Job Task Analysis) survey to determine objective weighting
# Develop exam content (aka exam items)
# Have a 305 Beta exam period for public feedback and testing
# Evaluation JTA and Beta exam results
# Launch final 305 exam

We are commencing this milestone 1 as described above and would like to have the final exam launch in 2011.
 

==How To Add to This Discussion==

Please add to the discussion on the lpi-examdev mailing list:

   http://list.lpi.org/mailman/listinfo/lpi-examdev

This page will be updated as we progress. Alternatively, register on this wiki and add your comments below.

==Topics to Be Considered for Coverage==

This is a brief list of topics under consideration:

Mail Services

* E-mail Concepts and Troubleshooting
* MTA (Postfix and/or Sendmail and/or Exim)
* IMAP/POP services (courier and/or dovecot and/or uw-imap)
* Virus scanning (Amavis)
* Spam filtering (SpamAssasin)
* MUA (Mail User Agents aka e-mail clients)
* Secure POP, IMAP, SMTP (setting up certificates, configuration)
* Integration with LDAP and/or MySQL
* greylisting
* blacklisting and RBLs

Messaging Services

* Messaging Servers (OpenFire and/or Jabberd)
* Messaging clients (Pidgin, Kopete)
* Messaging protocols (XMPP)
* Integration with LDAP and/or MySQL
* IRC clients and servers (maybe)

==Community Comments==

==The Minimally Qualified Candidate for This Exam==

This is a description of a Linux professional that is just barely
qualified to pass the LPI Level 3 Linux exams. This hypothetical person
is called the Minimally Qualified Candidate (MQC). Standards on the
Level 3 exams should be set so that this person (and anyone more able)
would pass but anyone less able would not pass.

An LPI certified Level 3 Linux professional (designated LPIC-3) should
have the technical capability to perform system administration at the
enterprise level. A [[LPIC-3]] certification holder should be able to understand, plan roll-outs,
install, configure, maintain and troubleshoot the technologies being
tested. These technologies differ for each exam but the level of ability
is at an enterprise level.

The LPIC-3 MQC typically (Yes, some of these bullets are specific to particular exams in the LPIC-3 series):

* Has installed and maintained Linux on a number of computers for various purposes for a number of years.
* Has integration experience with diverse technologies and operating systems.
* Has professional experience as, or training for, an enterprise level Linux professional. (Including having experience as a part of another role.)
* Is comfortable with advanced and enterprise levels of Linux administration including installation, management, security, troubleshooting and maintenance.
* Is able to use opensource tools to measure capacity planning and troubleshooting resource problems.
* Is able create scripts in Bash or Perl or has knowledge of at least one system programming language (such as C).
* Is able to plan, architecture, design, build and implement a full environment using E-mail and Messaging services as well as measure the capacity planning and security of the services.

LPIC-305

2010-09-13T15:33:48Z

StarnixAdmin: /* Topics to Be Considered for Coverage */

__FORCETOC__
==Introduction==
The description of the entire [[LPIC-3]] programme is listed [[LPIC-3|here]].

LPI is just getting underway in the development of the next LPIC-3 Enterprise exam. This exam will cover Mail and Messaging Services.

The main milestones to be achieved are:

# Consult with industry, partners and communities on requirements
# Create draft objectives
# Perform a JTA (Job Task Analysis) survey to determine objective weighting
# Develop exam content (aka exam items)
# Have a 305 Beta exam period for public feedback and testing
# Evaluation JTA and Beta exam results
# Launch final 305 exam

We are commencing this milestone 1 as described above and would like to have the final exam launch in 2011.
 

==How To Add to This Discussion==

Please add to the discussion on the lpi-examdev mailing list:

   http://list.lpi.org/mailman/listinfo/lpi-examdev

This page will be updated as we progress. Alternatively, register on this wiki and add your comments below.

==Topics to Be Considered for Coverage==

This is a brief list of topics under consideration:

Mail Services

* E-mail Concepts and Troubleshooting
* MTA (Postfix and/or Sendmail and/or Exim)
* IMAP/POP services (courier and/or dovecot and/or uw-imap)
* Virus scanning (Amavis)
* Spam filtering (SpamAssasin)
* MUA (Mail User Agents aka e-mail clients)
* Secure POP, IMAP, SMTP (setting up certificates, configuration)
* Integration with LDAP and/or MySQL
* greylisting
* blacklisting and RBLs

Messaging Services

* Messaging Servers (OpenFire and/or Jabberd)
* Messaging clients (Pidgin, Kopete)
* Messaging protocols (XMPP)
* Integration with LDAP and/or MySQL
* IRC clients and servers (maybe)

==Comments==

==The Minimally Qualified Candidate for This Exam==

This is a description of a Linux professional that is just barely
qualified to pass the LPI Level 3 Linux exams. This hypothetical person
is called the Minimally Qualified Candidate (MQC). Standards on the
Level 3 exams should be set so that this person (and anyone more able)
would pass but anyone less able would not pass.

An LPI certified Level 3 Linux professional (designated LPIC-3) should
have the technical capability to perform system administration at the
enterprise level. A [[LPIC-3]] certification holder should be able to understand, plan roll-outs,
install, configure, maintain and troubleshoot the technologies being
tested. These technologies differ for each exam but the level of ability
is at an enterprise level.

The LPIC-3 MQC typically (Yes, some of these bullets are specific to particular exams in the LPIC-3 series):

* Has installed and maintained Linux on a number of computers for various purposes for a number of years.
* Has integration experience with diverse technologies and operating systems.
* Has professional experience as, or training for, an enterprise level Linux professional. (Including having experience as a part of another role.)
* Is comfortable with advanced and enterprise levels of Linux administration including installation, management, security, troubleshooting and maintenance.
* Is able to use opensource tools to measure capacity planning and troubleshooting resource problems.
* Is able create scripts in Bash or Perl or has knowledge of at least one system programming language (such as C).
* Is able to plan, architecture, design, build and implement a full environment using E-mail and Messaging services as well as measure the capacity planning and security of the services.