|
|
|
[ Pobierz całość w formacie PDF ]
how it relates to Linux and the LPI exam. A good way to do this is by using hands-on exercises and examples
from real-world Linux systems whenever possible. For example, when discussing a configuration file in/etc,
give a sample of what a typical file might look like and encourage the reader to cat the file on their own sys-
tem.
Objectives may be grouped together when it is logical to do so.
4. Practice Questions
At the end of each chapter there should be a section dedicated to practice questions that cover the exam objec-
tives. These should not be verbatim questions from the exam! The idea is to let readers test their mastery of the
knowledge in each chapter and get a feel for the exam format, not to help them cheat. Anyone intentionally
submitting verbatim questions will be reported to the LPI and risks losing their certification.
1.2. DocBook XML Markup
The LPI Study Guide is written using DocBook XML markup. This allows the guide to be published in HTML, PDF
and other formats using the same source document. Those familiar with DocBook are encouraged to submit chapters
this way. Be sure to use markup for commands and filenames in addition to sections. Use the chapter on "Hardware
49
Documentation
& Architecture" as a template.
For those not familiar with DocBook should submit chapters in plain text in a format similar to the example below.
A Brief Look At The Objectives
Successful completion of the Hardware & Architecture section
of the LPI exam requires familiarity with Personal Computer
(PC) expansion cards [http://url-to-wikipedia/expansion-cards]...
Next-Section-Title
More text...
1.3. Additional Questions
Please email the author [mailto:dhorton.no-spam(at)no-spam.member.fsf.org] of the LPI study guide with any other
questions not covered.
2. Practice Questions
1. The command man -k passwd gives the same results as which one of the following commands:
A. whatis passwd
B. apropos passwd
C. passwd --help
D. info passwd
3. Answers To Practice Questions
1. The correct answer is B, man -k and apropos are equivalent. Answer A is incorrect, whatis is the same as man
-f. Answer C is incorrect, passwd --help gives a brief listing of command-line options and is unrelated to man
pages. Answer D is incorrect, info pages are part of a different documentation tool.
4. References
See the manual page for the man command.
50
Chapter 12. Shells, Scripting,
Programming and Compiling
1. This Chapter Is Up For Adoption
If you feel you are an expert in the subject area for this LPI topic and would like to write this chapter please email
the author [mailto:dhorton.no-spam(at)no-spam.member.fsf.org] of the LPI study guide to communicate your inten-
tions. Authors should be LPI certified or hold a similar certification in a related subject.
Please adopt only one chapter at a time and plan to finish the chapter within thirty days of adopting it.
More information about the study guide can be found at: http://www.happy-monkey.net/LPI/
1.1. Structuring The Chapter
The structure of chapters within the study guide needs to be consistent. The following structure may be used as a
guide. Authors are also encouraged to view the chapter covering "Hardware & Architecture" as a template.
1. Author Name
This is to ensure that authors get credit for their work. Please include your level of LPI certification after your
name. If there are other appropriate certifications, please include these as well. For example, someone writing a
chapter on networking might include the fact that they have a Cisco certification in addition to the LPI certifi-
cation like this: "Joe Smith, LPIC-1, CCNA".
2. A Brief Look At The Objectives
Each chapter should start with a high-level look at the LPI testing objectives. Within this "Brief Look" section
there should be hyperlinks to sources of additional information. For example, one might say, "The networking
section of the exam requires familiarity requires familiarity with IP addresses and subnet masks." The phrases
'IP addresses' and 'subnet masks' should be hyperlinked to additional information. Wikipedia is the prefered
source of external information, but it is also helpful to link to man pages for specific commands.
3. Detailed Discussion
Each one of the LPI exam objectives should receive a section for more detailed coverage of the objective and
how it relates to Linux and the LPI exam. A good way to do this is by using hands-on exercises and examples
from real-world Linux systems whenever possible. For example, when discussing a configuration file in/etc,
give a sample of what a typical file might look like and encourage the reader to cat the file on their own sys-
tem.
Objectives may be grouped together when it is logical to do so.
4. Practice Questions
At the end of each chapter there should be a section dedicated to practice questions that cover the exam objec-
tives. These should not be verbatim questions from the exam! The idea is to let readers test their mastery of the
knowledge in each chapter and get a feel for the exam format, not to help them cheat. Anyone intentionally
submitting verbatim questions will be reported to the LPI and risks losing their certification.
1.2. DocBook XML Markup
51
Shells, Scripting, Programming and
Compiling
The LPI Study Guide is written using DocBook XML markup. This allows the guide to be published in HTML, PDF
and other formats using the same source document. Those familiar with DocBook are encouraged to submit chapters
this way. Be sure to use markup for commands and filenames in addition to sections. Use the chapter on "Hardware
& Architecture" as a template.
For those not familiar with DocBook should submit chapters in plain text in a format similar to the example below.
A Brief Look At The Objectives
Successful completion of the Hardware & Architecture section
of the LPI exam requires familiarity with Personal Computer
(PC) expansion cards [http://url-to-wikipedia/expansion-cards]...
Next-Section-Title
More text...
1.3. Additional Questions
Please email the author [mailto:dhorton.no-spam(at)no-spam.member.fsf.org] of the LPI study guide with any other
questions not covered.
52
Chapter 13. Administrative Tasks
1. This Chapter Is Up For Adoption
If you feel you are an expert in the subject area for this LPI topic and would like to write this chapter please email
the author [mailto:dhorton.no-spam(at)no-spam.member.fsf.org] of the LPI study guide to communicate your inten-
tions. Authors should be LPI certified or hold a similar certification in a related subject.
Please adopt only one chapter at a time and plan to finish the chapter within thirty days of adopting it.
More information about the study guide can be found at: http://www.happy-monkey.net/LPI/
1.1. Structuring The Chapter
The structure of chapters within the study guide needs to be consistent. The following structure may be used as a
guide. Authors are also encouraged to view the chapter covering "Hardware & Architecture" as a template.
1. Author Name
This is to ensure that authors get credit for their work. Please include your level of LPI certification after your
name. If there are other appropriate certifications, please include these as well. For example, someone writing a
chapter on networking might include the fact that they have a Cisco certification in addition to the LPI certifi-
cation like this: "Joe Smith, LPIC-1, CCNA".
2. A Brief Look At The Objectives
[ Pobierz całość w formacie PDF ]
zanotowane.pldoc.pisz.plpdf.pisz.plkwiatpolny.htw.pl
|
|
| Cytat |
Dobre pomysły nie mają przeszłości, mają tylko przyszłość. Robert Mallet
De minimis - o najmniejszych rzeczach.
Dobroć jest ważniejsza niż mądrość, a uznanie tej prawdy to pierwszy krok do mądrości. Theodore Isaac Rubin
Dobro to tylko to, co szlachetne, zło to tylko to, co haniebne.
Dla człowieka nie tylko świat otaczający jest zagadką; jest on nią sam dla siebie. I z obu tajemnic bardziej dręczącą wydaje się ta druga. Antoni Kępiński (1918-1972)
|
|
