courses-commits September 2008

courses-commits@lists.stg.fedorahosted.org

1 participants
2 discussions

en-US/Book_Info.xml en-US/Books en-US/Courses.ent Makefile
by Jeroen van Meeuwen 25 Sep '08

25 Sep '08

Makefile | 4 en-US/Book_Info.xml | 4 en-US/Books/ClassRoom/Manual.xml | 2 en-US/Books/Linux/Advanced/Course.xml | 118 +++++++ en-US/Books/Linux/Senior/Course-Appendix.xml | 163 ++++++++++ en-US/Books/Linux/Senior/Course.xml | 428 +++++++++++++++++++++++++++ en-US/Courses.ent | 2 7 files changed, 714 insertions(+), 7 deletions(-) New commits: commit e513868e2e7e1c50042b8f031941ad4878d1572b Author: Jeroen van Meeuwen (Fedora Unity) <kanarip(a)fedoraunity.org> Date: Thu Sep 25 10:14:57 2008 +0200 updates diff --git a/Makefile b/Makefile index 7de69f3..81928e4 100644 --- a/Makefile +++ b/Makefile @@ -16,3 +16,7 @@ html: html-en-US fpeople: html rsync -aHvz --delete --progress --rsh=ssh tmp/en-US/html/ fedorapeople.org:./public_html/Courses/ + +kanarip: html + rsync -aHvz --delete --progress --rsh=ssh tmp/en-US/html/ pinky:/data/www/kanarip.com/www/public_html/courses/ + diff --git a/en-US/Book_Info.xml b/en-US/Book_Info.xml index 0b806bb..257bd6b 100644 --- a/en-US/Book_Info.xml +++ b/en-US/Book_Info.xml @@ -3,10 +3,12 @@ ]> <bookinfo id="CourseMaterials"> - <title>Course Materials for newbees</title> + <title>Courses</title> <subtitle></subtitle> <issuenum>0.1</issuenum> <productnumber>0</productnumber> + <edition>1</edition> + <pubsnumber>1</pubsnumber> <abstract><para>This book contains a number of courses applicable to You!</para></abstract> <corpauthor> <inlinemediaobject> diff --git a/en-US/Books/ClassRoom/Manual.xml b/en-US/Books/ClassRoom/Manual.xml index a170812..55c370c 100644 --- a/en-US/Books/ClassRoom/Manual.xml +++ b/en-US/Books/ClassRoom/Manual.xml @@ -53,7 +53,7 @@ </chapter> <chapter> - <title>Doing the work</title> + <title>Set Up The Class Room</title> <section id="ClassRoomManual-SettingUpClassRoom"> <title>Setting Up the Class Room</title> <para> diff --git a/en-US/Books/Linux/Advanced/Course.xml b/en-US/Books/Linux/Advanced/Course.xml index 954d572..46c0474 100644 --- a/en-US/Books/Linux/Advanced/Course.xml +++ b/en-US/Books/Linux/Advanced/Course.xml @@ -120,8 +120,57 @@ <chapter id="LinuxAdvancedCourse-SettingUpALAMPServer"> <title>Setting Up a LAMP Server</title> <para> - Something about packaging software. + In this chapter, you are going to set up a Linux, Apache, MySQL & PHP (LAMP) Server, with <application>phpMyAdmin</application> over SSL for MySQL administration by your users. </para> + + <section id="LinuxAdvancedCourse-SettingUpALAMPServer-Installation"> + <title>Installation</title> + <para> + To install Apache, MySQL & PHP, you need the following packages: + </para> + <para> + <itemizedlist> + <listitem> + <para> + <application>httpd</application> + </para> + </listitem> + <listitem> + <para> + <application>mysql</application> + </para> + </listitem> + <listitem> + <para> + <application>mysql-server</application> + </para> + </listitem> + <listitem> + <para> + <application>php</application> + </para> + </listitem> + <listitem> + <para> + <application>php-mysql</application> + </para> + </listitem> + </itemizedlist> + </para> + <para> + To install these packages, issue the following command: + </para> + <para> + <screen># yum install httpd mysql mysql-server php php-mysql</screen> + </para> + <warning> + <para> + When starting the MySQL service (<application>mysqld</application>), make sure you set a root password: + <screen># mysqladmin -u root password <emphasis>new-password</emphasis></screen> + </para> + </warning> + </section> + </chapter> <chapter id="LinuxAdvancedCourse-FileSharing"> @@ -141,8 +190,73 @@ <chapter id="LinuxAdvancedCourse-DNSAndDHCPServer"> <title>DNS And DHCP Server</title> <para> - Something about packaging software. + This chapter is about DNS and DHCP. </para> + + <section id="LinuxAdvancedCourse-DNSAndDHCPServer-BirdsViewOfDHCP"> + <title>Birds View Of DHCP</title> + <para> + The Dynamic Host Configuration Protocol is designed to enable a single node in the network to configure the other hosts with the necessary IP configuration for the network. In order to do so, such a node needs to be configured to allow DHCP queries to be performed and to answer appropriately, with the correct information for the DHCP client to function on the network. + </para> + <formalpara> + <title>How DHCP Works</title> + <para> + Here's an overview of how DHCP works, and what happens when a client requests IP configuration via DHCP: + </para> + </formalpara> + <para> + <itemizedlist> + <listitem> + <formalpara> + <title>Client sends out DHCP <emphasis>DISCOVER</emphasis></title> + <para> + This happens on UDP port 67, and because the client does not have any IP configuration yet, the target IP address for this broadcast is the overall broadcast address <code>255.255.255.255</code>, and not the network's broadcast address. Information contained in this DHCPDISCOVER message include the client's MAC address. + </para> + </formalpara> + </listitem> + <listitem> + <formalpara> + <title>Server(s) respond(s) with DHCP <emphasis>OFFER</emphasis></title> + <para> + One or more servers may respond with a DHCPOFFER, send back directly to the client (based on it's MAC address). These offers contain the basic IP configuration (IP address, netmask, gateway IP address). + </para> + </formalpara> + </listitem> + <listitem> + <formalpara> + <title>Client receives one or more DHCP <emphasis>OFFER</emphasis>(s)</title> + <para> + Although there is a routine to decide what DHCPOFFER, most often the client will take the offer that arrives first. The client, when receiving a DHCP offer, needs to check whether the IP address offered is free or already in use. It does so by performing an ARP look-up (Who has IP address X.X.X.X?). + </para> + </formalpara> + </listitem> + <listitem> + <formalpara> + <title>Client sends a DHCP <emphasis>REQUEST</emphasis></title> + <para> + If the IP address is free (or at this point so appears to be), then the client will send a DHCPREQUEST to the server that made the corresponding offer. Note that only one DHCPREQUEST at a time goes out in response to DHCPOFFER(s). + </para> + </formalpara> + </listitem> + <listitem> + <formalpara> + <title>Server sends a DHCP <emphasis>ACK</emphasis></title> + <para> + The server acknowledges the request from the client and the client can now configure it's interface with the IP address assigned. + </para> + </formalpara> + </listitem> + </itemizedlist> + </para> + + </section> + + <section id="LinuxAdvancedCourse-DNSAndDHCPServer-BirdsViewOfDNS"> + <title>Birds View Of DNS</title> + <para> + </para> + </section> + </chapter> <chapter id="LinuxAdvancedCourse-RouterAndOrFirewall"> diff --git a/en-US/Books/Linux/Senior/Course-Appendix.xml b/en-US/Books/Linux/Senior/Course-Appendix.xml index fb54899..36be332 100644 --- a/en-US/Books/Linux/Senior/Course-Appendix.xml +++ b/en-US/Books/Linux/Senior/Course-Appendix.xml @@ -4,10 +4,169 @@ <part id="LinuxSeniorCourse-Appendices"> <title>Appendices</title> - <appendix id="LinuxSeniorCourse-AppendixA"> - <title>Linux Senior Course Track AppendixA</title> + <appendix id="LinuxSeniorCourse-LPI101Questionnaire"> + <title>LPI 101 Questionnaire - Answers and Rationale</title> <para> + This appendix contains the answers and rationale for the questions in <xref linkend="LinuxSeniorCourse-LPI101-AssessmentQuestionaire" /> </para> + <para> + <segmentedlist> + <segtitle>Question #</segtitle> + <segtitle>Answer</segtitle> + <segtitle>Score</segtitle> + <segtitle>Your Score</segtitle> + <segtitle>Related Topic</segtitle> + <segtitle>Rationale</segtitle> + <seglistitem> + <seg>1</seg> + <seg>C</seg> + <seg>1</seg> + <seg></seg> + <seg><xref linkend="LinuxSeniorCourse-GNUAndUnixCommands-PerformBasicFileManagement" /></seg> + <seg><xref linkend="LinuxSeniorCourse-LPI101Questionnaire-Rationale-1" /></seg> + </seglistitem> + <seglistitem> + <seg>2</seg> + <seg>C</seg> + <seg>2</seg> + <seg></seg> + <seg><xref linkend="LinuxSeniorCourse-HardwareAndArchitecture-ConfigureFundamentalBIOSSettings-NormalBIOSSettings" /></seg> + <seg><xref linkend="LinuxSeniorCourse-LPI101Questionnaire-Rationale-2" /></seg> + </seglistitem> + <seglistitem> + <seg></seg> + <seg>B</seg> + <seg>1</seg> + <seg></seg> + <seg><xref linkend="LinuxSeniorCourse-HardwareAndArchitecture-ConfigureFundamentalBIOSSettings-NormalBIOSSettings" /></seg> + <seg><xref linkend="LinuxSeniorCourse-LPI101Questionnaire-Rationale-2" /></seg> + </seglistitem> + <seglistitem> + <seg>3</seg> + <seg>C</seg> + <seg>3</seg> + <seg></seg> + <seg><xref linkend="LinuxSeniorCourse-HardwareAndArchitecture-RAID" /></seg> + <seg><xref linkend="LinuxSeniorCourse-LPI101Questionnaire-Rationale-3" /></seg> + </seglistitem> + <seglistitem> + <seg>4</seg> + <seg>B</seg> + <seg>1</seg> + <seg></seg> + <seg><xref linkend="LinuxSeniorCourse-HardwareAndArchitecture-ConfigureFundamentalBIOSSettings-HardwareResources-IRQ" /></seg> + <seg><xref linkend="LinuxSeniorCourse-LPI101Questionnaire-Rationale-4" /></seg> + </seglistitem> + <seglistitem> + <seg>5</seg> + <seg>B</seg> + <seg>2</seg> + <seg></seg> + <seg><xref linkend="LinuxSeniorCourse-HardwareAndArchitecture-ConfigureFundamentalBIOSSettings-HardwareResources-IRQ" /></seg> + <seg><xref linkend="LinuxSeniorCourse-LPI101Questionnaire-Rationale-5" /></seg> + </seglistitem> + <seglistitem> + <seg>6</seg> + <seg>-</seg> + <seg>3</seg> + <seg></seg> + <seg><xref linkend="LinuxSeniorCourse-LinuxInstallationAndPackageManagement-MakeAndInstallProgramsFromSource" /></seg> + <seg><xref linkend="LinuxSeniorCourse-LPI101Questionnaire-Rationale-6" /></seg> + </seglistitem> + <seglistitem> + <seg>7</seg> + <seg>D</seg> + <seg>1</seg> + <seg></seg> + <seg></seg> + <seg></seg> + </seglistitem> + <seglistitem> + <seg>8</seg> + <seg>A</seg> + <seg>1</seg> + <seg></seg> + <seg></seg> + <seg></seg> + </seglistitem> + <seglistitem> + <seg>9</seg> + <seg>A, B, C and D</seg> + <seg>2</seg> + <seg></seg> + <seg></seg> + <seg><xref linkend="LinuxSeniorCourse-LPI101Questionnaire-Rationale-9" /></seg> + </seglistitem> + <seglistitem> + <seg></seg> + <seg></seg> + <seg></seg> + <seg></seg> + <seg>Your Total Score</seg> + </seglistitem> + </segmentedlist> + </para> + + <formalpara id="LinuxSeniorCourse-LPI101Questionnaire-Rationale-1"> + <title>Question 1 - Rationale</title> + <para> + <application>df -h</application> of course shows you disk usage information per mounted partition. <application>du -sh .</application> gets you close to the correct answer, but only shows the total amount of disk space used by the current working directory, in the given scenario <filename>/usr/share/</filename>. <application>ls -lah</application> then again just gives you the directory contents, and describes the size of the files in the current working directory, but does not cumulate what is in the directories residing in the current working directory, nor cumulates the overall size of the current working directory. <application>du -sch *</application> is the correct answer here (and you may have chosen that answer directly instead of eliminating all other options). + </para> + </formalpara> + + <formalpara id="LinuxSeniorCourse-LPI101Questionnaire-Rationale-2"> + <title>Question 2 - Rationale</title> + <para> + </para> + </formalpara> + + <formalpara id="LinuxSeniorCourse-LPI101Questionnaire-Rationale-3"> + <title>Question 3 - Rationale</title> + <para> + A webserver that is business critical is supposed to remain in a running state no matter what happens. This is a reason to make the operating system's root filesystem a redundant RAID set. The content served is extremely critical as well, and in comparison to the operating system itself, much harder to recover, and much more likely subject to change. This is a reason to make the <filename>/var/www/</filename> even more redundant, such as with RAID-5 or RAID-1 including a hot spare. We choose to use RAID-1 with a hot spare so that one disk can break down, without needing to be replaced immediately. In a RAID-5 set, you have a write performance advantage, but a web server is unlikely to write that much. However only one disk can break down at the same time. In a RAID-1 set with a hot-spare however, you have some time to replace the failed disk and meanwhile the set remains it's redundancy. + </para> + </formalpara> + <para> + Note that we do not mention anything about databases running from this server. Given the scenario however, you may conclude that it is a web server, and not a hybrid web- and database server. + </para> + + <formalpara id="LinuxSeniorCourse-LPI101Questionnaire-Rationale-4"> + <title>Question 4 - Rationale</title> + <para> + </para> + </formalpara> + + <formalpara id="LinuxSeniorCourse-LPI101Questionnaire-Rationale-5"> + <title>Question 5 - Rationale</title> + <para> + </para> + </formalpara> + + <formalpara id="LinuxSeniorCourse-LPI101Questionnaire-Rationale-6"> + <title>Question 6 - Rationale</title> + <para> + </para> + </formalpara> + + <formalpara id="LinuxSeniorCourse-LPI101Questionnaire-Rationale-7"> + <title>Question 7 - Rationale</title> + <para> + </para> + </formalpara> + + <formalpara id="LinuxSeniorCourse-LPI101Questionnaire-Rationale-8"> + <title>Question 8 - Rationale</title> + <para> + </para> + </formalpara> + + <formalpara id="LinuxSeniorCourse-LPI101Questionnaire-Rationale-9"> + <title>Question 9 - Rationale</title> + <para> + The only reason <filename>/usr/</filename> has to be on the root partition is because the mount point has to be available. + </para> + </formalpara> + </appendix> <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </part> diff --git a/en-US/Books/Linux/Senior/Course.xml b/en-US/Books/Linux/Senior/Course.xml index 998752c..1a60dc7 100644 --- a/en-US/Books/Linux/Senior/Course.xml +++ b/en-US/Books/Linux/Senior/Course.xml @@ -1277,6 +1277,434 @@ Working Devices : 4 </chapter> + <chapter id="LinuxSeniorCourse-LPI101-AssessmentQuestionaire"> + <title>Assessment Questionaire</title> + <para> + This is an assessment questionaire you can use to review what topics you need to pass by before doing the exam. Note that these are not the same questions you get on the LPI exam, and this questionnaire can be considered a little more difficult. + </para> + + <section id="LinuxSeniorCourse-LPI101-AssessmentQuestionaire-HowThisWorks"> + <title>How this works</title> + <para> + The questionaire contains a number of questions you can use to review your knowledge and chances when taking the exam. In Appendix FOO, the correct answers as well as references to the correct topics (both in this set of books as well as the Internet), and a score diagram. + </para> + </section> + + <section id="LinuxSeniorCourse-LPI101-AssessmentQuestionaire-Questions"> + <title>Questionaire</title> + <para> + <orderedlist numeration="arabic"> + <listitem> + <para> + You have navigated into the directory <filename>/usr/share/</filename>. Which of the following commands would you use to see how much disk space in total, as well as each directory seperately, is consumed? Select the best of all answers. + <orderedlist numeration="upperalpha" continuation="restarts"> + <listitem> + <para> + <application>df -h</application> + </para> + </listitem> + <listitem> + <para> + <application>du -sh .</application> + </para> + </listitem> + <listitem> + <para> + <application>du -sch *</application> + </para> + </listitem> + <listitem> + <para> + <application>ls -lah</application> + </para> + </listitem> + </orderedlist> + </para> + </listitem> + <listitem> + <para> + You have inserted a new hard drive in a computer, which now has two hard drives, and the computer won't boot properly anymore. Without the error message, what would you think is the most likely reason? Select what you think is the best answer. + <orderedlist numeration="upperalpha" continuation="restarts"> + <listitem> + <para> + You have not connected the new hard drive properly. + </para> + </listitem> + <listitem> + <para> + The hard drive that was in the computer is not the primary hard drive anymore, and the BIOS looks at the new hard drive seeking a boot sector, but you haven't had a chance to partition, format and make it bootable, yet. + </para> + </listitem> + <listitem> + <para> + <filename>/etc/fstab</filename> says to mount <filename>/dev/hda2</filename> as the root filesystem, but <filename>/dev/hda</filename> is the new hard drive, and the root filesystem is on the old hard drive. Hence the operating system cannot find and mount the root filesystem and the operating system is prevented from booting up properly. + </para> + </listitem> + <listitem> + <para> + The boot sequence in the BIOS is off and the computer just won't boot from any hard drive, at all. + </para> + </listitem> + </orderedlist> + </para> + </listitem> + <listitem> + <para> + You are asked to install a business critical web server for a large company. You order a machine with 5 hard drives and a hardware RAID controller. You receive the machine and are now required to install it. Which do you think is the best RAID and partitioning layout? + <orderedlist numeration="upperalpha" continuation="restarts"> + <listitem> + <para> + One disk will be used for the operating system (root filesystem), and the other 4 disks are setup in a RAID-0 set, mounted under <filename>/var/www/</filename>. + </para> + </listitem> + <listitem> + <para> + Two disks go in RAID-1 for the operating system. The three other disks go in RAID-5 and are mounted under <filename>/var/www/</filename>. + </para> + </listitem> + <listitem> + <para> + Two disks go in RAID-1 for the operating system. The three other disks go in RAID-1 with one hot spare, and are mounted under <filename>/var/www/</filename>. + </para> + </listitem> + <listitem> + <para> + FIXME + </para> + </listitem> + </orderedlist> + </para> + </listitem> + <listitem> + <para> + To determine whether there is conflicting IRQ assigned, what command would you use? + <orderedlist numeration="upperalpha" continuation="restarts"> + <listitem> + <para> + <application>cat /proc/irq</application> + </para> + </listitem> + <listitem> + <para> + <application>cat /proc/interrupts</application> + </para> + </listitem> + <listitem> + <para> + <application>lspci</application> + </para> + </listitem> + <listitem> + <para> + <application>lshal</application> + </para> + </listitem> + </orderedlist> + </para> + </listitem> + <listitem> + <para> + What is the default IRQ for COM1 (or <emphasis>ttyS0</emphasis>)? + <orderedlist numeration="upperalpha" continuation="restarts"> + <listitem> + <para> + 0x3f8 + </para> + </listitem> + <listitem> + <para> + 4 + </para> + </listitem> + <listitem> + <para> + 3 + </para> + </listitem> + <listitem> + <para> + 0x2f8 + </para> + </listitem> + </orderedlist> + </para> + </listitem> + <listitem> + <para> + What would be the correct sequence of commands to compile a program for a dual-core processor? + <orderedlist numeration="upperalpha" continuation="restarts"> + <listitem> + <para> + <code>./configure; make</code> + </para> + </listitem> + <listitem> + <para> + <code>./configure; make -j2</code> + </para> + </listitem> + <listitem> + <para> + <code>./configure; make -j3</code> + </para> + </listitem> + <listitem> + <para> + <code>./configure; make; make install</code> + </para> + </listitem> + </orderedlist> + </para> + </listitem> + <listitem> + <para> + Which of the following partition types cannot contain a root filesystem? Select all that apply. + <orderedlist numeration="upperalpha" continuation="restarts"> + <listitem> + <para> + Primary + </para> + </listitem> + <listitem> + <para> + Extended + </para> + </listitem> + <listitem> + <para> + Logical + </para> + </listitem> + <listitem> + <para> + None of the above + </para> + </listitem> + </orderedlist> + </para> + </listitem> + <listitem> + <para> + How many primary partitions can a disk contain? + <orderedlist numeration="upperalpha" continuation="restarts"> + <listitem> + <para> + 4 + </para> + </listitem> + <listitem> + <para> + 5 + </para> + </listitem> + <listitem> + <para> + 2 + </para> + </listitem> + <listitem> + <para> + 3 + </para> + </listitem> + </orderedlist> + </para> + </listitem> + <listitem> + <para> + Which of the following directories is required to be on the root partition? Select all that apply. + <orderedlist numeration="upperalpha" continuation="restarts"> + <listitem> + <para> + <filename>/bin/</filename> + </para> + </listitem> + <listitem> + <para> + <filename>/usr/</filename> + </para> + </listitem> + <listitem> + <para> + <filename>/etc/</filename> + </para> + </listitem> + <listitem> + <para> + <filename>/sbin/</filename> + </para> + </listitem> + </orderedlist> + </para> + </listitem> + <listitem> + <para> + Question + <orderedlist numeration="upperalpha" continuation="restarts"> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + </orderedlist> + </para> + </listitem> + <listitem> + <para> + Question + <orderedlist numeration="upperalpha" continuation="restarts"> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + </orderedlist> + </para> + </listitem> + <listitem> + <para> + Question + <orderedlist numeration="upperalpha" continuation="restarts"> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + </orderedlist> + </para> + </listitem> + <listitem> + <para> + Question + <orderedlist numeration="upperalpha" continuation="restarts"> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + </orderedlist> + </para> + </listitem> + <listitem> + <para> + Question + <orderedlist numeration="upperalpha" continuation="restarts"> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + </orderedlist> + </para> + </listitem> + <listitem> + <para> + Question + <orderedlist numeration="upperalpha" continuation="restarts"> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + <listitem> + <para> + Answer + </para> + </listitem> + </orderedlist> + </para> + </listitem> + </orderedlist> + </para> + </section> + + </chapter> + </part> <part id="LinuxSeniorCourse-LPI102"> diff --git a/en-US/Courses.ent b/en-US/Courses.ent index 30ae573..615f41e 100644 --- a/en-US/Courses.ent +++ b/en-US/Courses.ent @@ -1,4 +1,4 @@ <!ENTITY PRODUCT "Documentation"> -<!ENTITY BOOKID "CSI"> +<!ENTITY BOOKID "Courses"> <!ENTITY YEAR "2008"> <!ENTITY HOLDER "Jeroen van Meeuwen">

1 0

en-US/Books en-US/Courses.xml
by Jeroen van Meeuwen 10 Sep '08

10 Sep '08

en-US/Books/Linux/RHCETraining/Author_Group.xml | 24 + en-US/Books/Linux/RHCETraining/Course-Appendix.xml | 13 en-US/Books/Linux/RHCETraining/Course-Book_Info.xml | 27 ++ en-US/Books/Linux/RHCETraining/Course-Preface.xml | 11 en-US/Books/Linux/RHCETraining/Course.xml | 51 +++ en-US/Books/Linux/RHCETraining/Manual-Appendix.xml | 13 en-US/Books/Linux/RHCETraining/Manual-Book_Info.xml | 27 ++ en-US/Books/Linux/RHCETraining/Manual-Preface.xml | 11 en-US/Books/Linux/RHCETraining/Manual.xml | 39 ++ en-US/Books/Linux/RHCETraining/Revision_History.xml | 26 + en-US/Books/Linux/Senior/Course.xml | 115 ++++++++ en-US/Books/Linux/Senior/Manual-Appendix.xml | 263 +++++++++++++------- en-US/Books/Linux/Senior/Manual.xml | 4 en-US/Courses.xml | 23 + 14 files changed, 558 insertions(+), 89 deletions(-) New commits: commit 6cf44cd9862db7d0e1634410cadc0941fd1131f0 Author: Jeroen van Meeuwen (Fedora Unity) <kanarip(a)fedoraunity.org> Date: Wed Sep 10 09:58:48 2008 +0200 Updates diff --git a/en-US/Books/Linux/RHCETraining/Author_Group.xml b/en-US/Books/Linux/RHCETraining/Author_Group.xml new file mode 100644 index 0000000..c9ba622 --- /dev/null +++ b/en-US/Books/Linux/RHCETraining/Author_Group.xml @@ -0,0 +1,24 @@ +<?xml version='1.0'?> +<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> + +<authorgroup> + <author> + <firstname>Jeroen</firstname> + <surname>van Meeuwen</surname> + <affiliation> + <orgname>Operator Groep Delft</orgname> + <orgdiv>Sr. System Engineer</orgdiv> + </affiliation> + <email>j.van.meeuwen(a)ogd.nl</email> + </author> + <author> + <firstname>Stefan</firstname> + <surname>Hartsuiker</surname> + <affiliation> + <orgname>Operator Groep Delft</orgname> + <orgdiv>System Engineer</orgdiv> + </affiliation> + <email>s.hartsuiker(a)ogd.nl</email> + </author> +</authorgroup> diff --git a/en-US/Books/Linux/RHCETraining/Course-Appendix.xml b/en-US/Books/Linux/RHCETraining/Course-Appendix.xml new file mode 100644 index 0000000..a687d4a --- /dev/null +++ b/en-US/Books/Linux/RHCETraining/Course-Appendix.xml @@ -0,0 +1,13 @@ +<?xml version='1.0'?> +<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> + +<part id="RHCETrainingCourse-Appendices"> + <title>Appendices</title> + <appendix id="RHCETrainingCourse-AppendixA"> + <title>RHCE Training Course AppendixA</title> + <para> + </para> + </appendix> + <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> +</part> diff --git a/en-US/Books/Linux/RHCETraining/Course-Book_Info.xml b/en-US/Books/Linux/RHCETraining/Course-Book_Info.xml new file mode 100644 index 0000000..df4c47f --- /dev/null +++ b/en-US/Books/Linux/RHCETraining/Course-Book_Info.xml @@ -0,0 +1,27 @@ +<?xml version='1.0'?> +<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> + +<bookinfo id="RHCETrainingCourse-Product_Name_and_Version"> + <title>RHCE Training Course</title> + <subtitle>RHCE Training Course</subtitle> + <issuenum>0.1</issuenum> + <productnumber>1</productnumber> + <abstract><para>This book is about... (Be brief; this para is used for the RPM spec file)</para></abstract> + <corpauthor> + <inlinemediaobject> + <imageobject> + <imagedata format='SVG' fileref="Common_Content/images/title_logo.svg" /> + </imageobject> + </inlinemediaobject> + </corpauthor> + <copyright> + <year>&YEAR;</year> + <holder>&HOLDER;</holder> + </copyright> + <xi:include href="../../../Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> +</bookinfo> + + + diff --git a/en-US/Books/Linux/RHCETraining/Course-Preface.xml b/en-US/Books/Linux/RHCETraining/Course-Preface.xml new file mode 100644 index 0000000..60125a1 --- /dev/null +++ b/en-US/Books/Linux/RHCETraining/Course-Preface.xml @@ -0,0 +1,11 @@ +<?xml version='1.0'?> +<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> + +<preface id="RHCETrainingCourse-Preface"> + <title>Preface</title> + <para> + </para> + <xi:include href="../../../Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="../../../Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> +</preface> diff --git a/en-US/Books/Linux/RHCETraining/Course.xml b/en-US/Books/Linux/RHCETraining/Course.xml new file mode 100644 index 0000000..d7e2f08 --- /dev/null +++ b/en-US/Books/Linux/RHCETraining/Course.xml @@ -0,0 +1,51 @@ +<?xml version="1.0" encoding="utf-8"?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd"> + +<book id="RHCETrainingCourse"> + + <xi:include href="Course-Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Course-Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <part id="RHCETrainingCourse-Part"> + <title>RHCE Training Course</title> + <chapter id="RHCETrainingCourse-Introduction"> + <title>Introduction</title> + <para> + This book is (...) + </para> + + <section id="RHCETrainingCourse-First_Section"> + <title>First Section</title> + <para> + This is a first section + </para> + </section> + +  + + <section id="SELinux"> + <title>SELinux</title> + <para> + </para> + </section> + + </chapter> + </part> + + <xi:include href="Course-Appendix.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + +</book> + + + + diff --git a/en-US/Books/Linux/RHCETraining/Manual-Appendix.xml b/en-US/Books/Linux/RHCETraining/Manual-Appendix.xml new file mode 100644 index 0000000..c0fbba2 --- /dev/null +++ b/en-US/Books/Linux/RHCETraining/Manual-Appendix.xml @@ -0,0 +1,13 @@ +<?xml version='1.0'?> +<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> + +<part id="RHCETrainingManual-Appendices"> + <title>Appendices</title> + <appendix id="RHCETrainingManual-AppendixA"> + <title>RHCE Training Manual AppendixA</title> + <para> + </para> + </appendix> + <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> +</part> diff --git a/en-US/Books/Linux/RHCETraining/Manual-Book_Info.xml b/en-US/Books/Linux/RHCETraining/Manual-Book_Info.xml new file mode 100644 index 0000000..0617a41 --- /dev/null +++ b/en-US/Books/Linux/RHCETraining/Manual-Book_Info.xml @@ -0,0 +1,27 @@ +<?xml version='1.0'?> +<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> + +<bookinfo id="RHCETrainingManual-Product_Name_and_Version"> + <title>RHCE Training Manual</title> + <subtitle>RHCE Training Manual</subtitle> + <issuenum>0.1</issuenum> + <productnumber>1</productnumber> + <abstract><para>This book is about... (Be brief; this para is used for the RPM spec file)</para></abstract> + <corpauthor> + <inlinemediaobject> + <imageobject> + <imagedata format='SVG' fileref="Common_Content/images/title_logo.svg" /> + </imageobject> + </inlinemediaobject> + </corpauthor> + <copyright> + <year>&YEAR;</year> + <holder>&HOLDER;</holder> + </copyright> + <xi:include href="../../../Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> +</bookinfo> + + + diff --git a/en-US/Books/Linux/RHCETraining/Manual-Preface.xml b/en-US/Books/Linux/RHCETraining/Manual-Preface.xml new file mode 100644 index 0000000..a89c306 --- /dev/null +++ b/en-US/Books/Linux/RHCETraining/Manual-Preface.xml @@ -0,0 +1,11 @@ +<?xml version='1.0'?> +<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> + +<preface id="RHCETrainingManual-Preface"> + <title>Preface</title> + <para> + </para> + <xi:include href="../../../Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="../../../Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> +</preface> diff --git a/en-US/Books/Linux/RHCETraining/Manual.xml b/en-US/Books/Linux/RHCETraining/Manual.xml new file mode 100644 index 0000000..5f0e857 --- /dev/null +++ b/en-US/Books/Linux/RHCETraining/Manual.xml @@ -0,0 +1,39 @@ +<?xml version="1.0" encoding="utf-8"?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd"> + +<book id="RHCETrainingManual"> + + <xi:include href="Manual-Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Manual-Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <part id="RHCETrainingManual-Part"> + <title>RHCE Training Manual</title> + <chapter id="RHCETrainingManual-Introduction"> + <title>Introduction</title> + <para> + This book is (...) + </para> + + <section id="RHCETrainingManual-First_Section"> + <title>First Section</title> + <para> + This is a first section + </para> + </section> + + </chapter> + </part> + + <xi:include href="Manual-Appendix.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + +</book> + + + + diff --git a/en-US/Books/Linux/RHCETraining/Revision_History.xml b/en-US/Books/Linux/RHCETraining/Revision_History.xml new file mode 100644 index 0000000..fda893e --- /dev/null +++ b/en-US/Books/Linux/RHCETraining/Revision_History.xml @@ -0,0 +1,26 @@ +<?xml version='1.0'?> +<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> + +<appendix> + <title>Revision History</title> + <para> + <revhistory> + <revision> + <revnumber>1.0</revnumber> + <date></date> + <author> + <firstname></firstname> + <surname></surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member></member> + </simplelist> + </revdescription> + </revision> + </revhistory> + </para> +</appendix> + diff --git a/en-US/Books/Linux/Senior/Course.xml b/en-US/Books/Linux/Senior/Course.xml index 4e60155..998752c 100644 --- a/en-US/Books/Linux/Senior/Course.xml +++ b/en-US/Books/Linux/Senior/Course.xml @@ -861,6 +861,55 @@ ERR: 0 <para> Nowadays, most end-user desktop systems have some form of a "hardware RAID controller" integrated on the mainboard. This hardware RAID controller however isn't <emphasis>hardware RAID</emphasis> like we just defined, and still requires the operating system to handle RAID. In Windows systems, this often requires you to supply the chipset's driver during the installation (if the disks attached to the controller are to be the boot or system partition), or afterwards, to be able to use the disks. On Linux systems, although most of the controllers are supported, creating the bootable partition on a disk attached to such controller would require you to supply the driver disk as well. </para> + <para> + When using Software RAID, you tell the operating system to use a set of equally sized partitions at a certain RAID level. Here's an example of a machine with 8 hard disks, of which one (<filename>/dev/sda</filename>) is the operating system disk holding <filename>/</filename> and <filename>/boot</filename>, and two RAID arrays; one in level 5 and one in level 0. The 8th disk (<filename>/dev/sdd</filename>) is used for another partition: + </para> + <para> + <screen># <userinput>cat /proc/mdstat</userinput> +Personalities : [raid6] [raid5] [raid4] [raid0] +md1 : active raid5 sde1[0] sdh1[3] sdg1[2] sdf1[1] + 360160896 blocks level 5, 4k chunk, algorithm 2 [4/4] [UUUU] + +md0 : active raid0 sdc1[1] sdb1[0] + 156296192 blocks 64k chunks + +unused devices: <none></screen> + </para> + <para> + As you can see the operating system sees each separate device, uses one partition on each of these devices and treats them as parts of a RAID set. <code>md1</code> in this case spans 4 partitions for a RAID level 5 array, which means there is 4 disks in the RAID array: + </para> + <para> + <screen># <userinput>mdadm --misc -D /dev/md1</userinput> +/dev/md1: + Version : 00.90.03 + Creation Time : Sun Nov 4 02:02:17 2007 + Raid Level : raid5 + Array Size : 360160896 (343.48 GiB 368.80 GB) + Used Dev Size : 120053632 (114.49 GiB 122.93 GB) + Raid Devices : 4 + Total Devices : 4 +Preferred Minor : 1 + Persistence : Superblock is persistent + + Update Time : Sun Aug 31 21:56:18 2008 + State : active + Active Devices : 4 +Working Devices : 4 + Failed Devices : 0 + Spare Devices : 0 + + Layout : left-symmetric + Chunk Size : 4K + + UUID : 1fe73af9:646a76f6:fc270fd4:e15e074d + Events : 0.15 + + Number Major Minor RaidDevice State + 0 8 65 0 active sync /dev/sde1 + 1 8 81 1 active sync /dev/sdf1 + 2 8 97 2 active sync /dev/sdg1 + 3 8 113 3 active sync /dev/sdh1</screen> + </para> </section> </section> @@ -984,8 +1033,72 @@ ERR: 0 <section id="LinuxSeniorCourse-LinuxInstallationAndPackageManagement-DesignHardDiskLayout"> <title>Design Hard Disk Layout</title> <para> - When designing a hard disk layout most importantly you will want to predict where data is going to end up on the running system. If you install a webserver, most data will probably be in <filename>/var/</filename>, including <filename>/var/lib/mysql/</filename>, <filename>/var/lib/pgsql/</filename>, and most importantly, <filename>/var/www/</filename>. + When designing a hard disk layout most importantly you will want to predict where data is going to end up on the running system. If you install a webserver, most data will probably be in <filename>/var/</filename>, including <filename>/var/lib/mysql/</filename>, <filename>/var/lib/pgsql/</filename>, and most importantly, <filename>/var/www/</filename>. A fileserver on the other hand may need a larger <filename>/home/</filename> partition. </para> + <para> + Amongst the future function(s) of the system, there are a few other things to consider in designing the hard disk layout: + <itemizedlist> + <listitem> + <formalpara> + <title>The total amount of disk space</title> + <para> + These days, while disk space is (really really) cheap, this item will most likely not apply to any given new system... However, on systems with just a tiny small bit of storage, you may need to reconsider how you normally partition the system. A few MB (~100) is needed for a boot partition, and a few MB (~100-150) is recommended for swap space. The rest of the tiny hard drive can be used for the <filename>/</filename> (root) filesystem. + </para> + </formalpara> + </listitem> + <listitem> + <formalpara> + <title>The overall size of the system</title> + <para> + With the overall size of the system, we do not mean the form factor. The overall purpose of the machine and it's size within the organization is what we mean by the size of the system. A <filename>/home/</filename> fileserver for 3 users is smaller then a <filename>/home/</filename> and <filename>/data/</filename> group share fileserver for a 1.500 user organisation, of course. This is an additional hard disk layout consideration. + </para> + </formalpara> + <para> + Also, you should very carefully consider what type of I/O the system is going to perform on certain partitions. A share of <filename>/usr/</filename> is going to be read <emphasis>a lot</emphasis>, but written to just a little. You may want to choose for a perfomance vs. redundancy configuration for this partition, such as RAID-5 with 3 or more disks. Additionally, for a <filename>/data/</filename> group share volume, you may want to consider that the I/O in both writing and reading operations, as well as the importance of the volume. + </para> + </listitem> + <listitem> + <formalpara> + <title>The backup strategy for the system</title> + <para> + If a backup strategy is to backup the entire machine just once a year, you may want to guarantee the volumes' integrity as much as you can by making it fully redundant (RAID-1, hot spare), whereas a system that is backed up daily may suffice with a RAID-5 (no hot spare) volume configuration. + </para> + </formalpara> + </listitem> + </itemizedlist> + </para> + <para> + As a rule of thumb, swap space is usually twice as large as the amount of memory for a system. However, since even a normal end-user desktop has 2GB easily nowadays, creating as much as 4GB swap space is pointless. Swap in a Linux system is used when the system runs out of regular memory and wants to preserve some of the pages in memory. This shouldn't be more then the amount of system memory for recent machines anyway, and the larger the amount of memory available in a system, the smaller the swap space can be. Note that for machines that only have 512MB memory, configuring a swap space of between 1GB and 1.5GB is not a bad idea. Systems with 4GB memory however will not likely ever need more then 1GB of swap space. + </para> + + <section id="LinuxSeniorCourse-LinuxInstallationAndPackageManagement-DesignHardDiskLayout-WhereDoFilesGo"> + <title>Where Do Files Go?</title> + <para> + When designing a hard disk layout, it is important you know where files are supposed to go on a given system. Conforming the hierarchy of directory trees on the system to the <link linkend="LinuxSeniorCourse-DevicesLinuxFilesystemsAndTheFHS-FindSystemFilesAndPlaceFilesInTheCorrectLocation">File Hierarchy Standard (FHS)</link> is not only recommended, it is also required for systems running <link linkend="SELinux">SELinux</link>. + </para> + <para> + An overview of requirements and recommendations to various directories and the partitions they are on: + <itemizedlist> + <listitem> + <formalpara> + <title><filename>/boot/</filename></title> + <para> + The boot partition should be no smaller then twice the size of a single kernel, a single initial ramdisk, the bootloader stage 1.5 and stage 2 files, and the bootloader's configuration file. It should also not be larger then what the system allows within the first 1024 cylinders of the hard disk. See also: <xref linkend="LinuxSeniorCourse-HardwareAndArchitecture-ConfigureFundamentalBIOSSettings-TheMagical1024Limit" /> + </para> + </formalpara> + </listitem> + <listitem> + <formalpara> + <title><filename>/etc/</filename></title> + <para> + The <filename>/etc/</filename> should always be on the same partition as the <filename>/</filename> (root) filesystem. The <filename>/etc/</filename> directory contains all configuration files for the local system, including <filename>/etc/fstab</filename>, which by design is loaded by the initial ramdisk from the root filesystem to mount the partitions and devices configured to be mounted. The root filesystem in turn is a configurable option to pass on the kernel's <application>cmdline</application>. + </para> + </formalpara> + </listitem> + </itemizedlist> + </para> + </section> + </section> <section id="LinuxSeniorCourse-LinuxInstallationAndPackageManagement-InstallABootManager"> diff --git a/en-US/Books/Linux/Senior/Manual-Appendix.xml b/en-US/Books/Linux/Senior/Manual-Appendix.xml index 06c2854..28ad2e4 100644 --- a/en-US/Books/Linux/Senior/Manual-Appendix.xml +++ b/en-US/Books/Linux/Senior/Manual-Appendix.xml @@ -6,92 +6,183 @@ <title>Appendices</title> <appendix id="LinuxSeniorManual-Appendix-ExampleCourseSchedule"> <title>Example Course Schedule</title> - <para> - <segmentedlist> - <segtitle>Week #</segtitle> - <segtitle>Date</segtitle> - <segtitle>Day Description</segtitle> - <segtitle>Start / End</segtitle> - <seglistitem> - <seg>1</seg> - <seg></seg> - <seg>Kickoff Meeting</seg> - <seg>18:30 - 20:30</seg> - </seglistitem> - <seglistitem> - <seg>2</seg> - <seg></seg> - <seg>LPI-101 Course Day</seg> - <seg>9:30 - 17:30</seg> - </seglistitem> - <seglistitem> - <seg>3</seg> - <seg></seg> - <seg>LPI-101 Course Evening</seg> - <seg>18:30 - 22:30</seg> - </seglistitem> - <seglistitem> - <seg>4</seg> - <seg></seg> - <seg>Exam LPI-101</seg> - <seg></seg> - </seglistitem> - <seglistitem> - <seg>5</seg> - <seg></seg> - <seg>LPI-102 Course Day</seg> - <seg>9:30 - 17:30</seg> - </seglistitem> - <seglistitem> - <seg>6</seg> - <seg></seg> - <seg>LPI-202 Course Evening</seg> - <seg>18:30 - 22:30</seg> - </seglistitem> - <seglistitem> - <seg>7</seg> - <seg></seg> - <seg>Exam LPI-102</seg> - <seg></seg> - </seglistitem> - <seglistitem> - <seg>8</seg> - <seg></seg> - <seg>LPI-201 Course Day</seg> - <seg>9:30 - 17:30</seg> - </seglistitem> - <seglistitem> - <seg>9</seg> - <seg></seg> - <seg>LPI-201 Course Evening</seg> - <seg>18:30 - 22:30</seg> - </seglistitem> - <seglistitem> - <seg>10</seg> - <seg></seg> - <seg>Exam LPI-201</seg> - <seg></seg> - </seglistitem> - <seglistitem> - <seg>11</seg> - <seg></seg> - <seg>LPI-202 Course Day</seg> - <seg>9:30 - 17:30</seg> - </seglistitem> - <seglistitem> - <seg>12</seg> - <seg></seg> - <seg>LPI-202 Course Evening</seg> - <seg>18:30 - 22:30</seg> - </seglistitem> - <seglistitem> - <seg>13</seg> - <seg></seg> - <seg>Exam LPI-202</seg> - <seg></seg> - </seglistitem> - </segmentedlist> - </para> + <para> + <segmentedlist> + <segtitle>Week #</segtitle> + <segtitle>Date</segtitle> + <segtitle>Day Description</segtitle> + <segtitle>Start / End</segtitle> + <seglistitem> + <seg>1</seg> + <seg></seg> + <seg>Kickoff Meeting</seg> + <seg>18:30 - 20:30</seg> + </seglistitem> + <seglistitem> + <seg>2</seg> + <seg></seg> + <seg>LPI-101 Course Day</seg> + <seg>9:30 - 17:30</seg> + </seglistitem> + <seglistitem> + <seg>3</seg> + <seg></seg> + <seg>LPI-101 Course Evening</seg> + <seg>18:30 - 22:30</seg> + </seglistitem> + <seglistitem> + <seg>4</seg> + <seg></seg> + <seg>Exam LPI-101</seg> + <seg></seg> + </seglistitem> + <seglistitem> + <seg>5</seg> + <seg></seg> + <seg>LPI-102 Course Day</seg> + <seg>9:30 - 17:30</seg> + </seglistitem> + <seglistitem> + <seg>6</seg> + <seg></seg> + <seg>LPI-202 Course Evening</seg> + <seg>18:30 - 22:30</seg> + </seglistitem> + <seglistitem> + <seg>7</seg> + <seg></seg> + <seg>Exam LPI-102</seg> + <seg></seg> + </seglistitem> + <seglistitem> + <seg>8</seg> + <seg></seg> + <seg>LPI-201 Course Day</seg> + <seg>9:30 - 17:30</seg> + </seglistitem> + <seglistitem> + <seg>9</seg> + <seg></seg> + <seg>LPI-201 Course Evening</seg> + <seg>18:30 - 22:30</seg> + </seglistitem> + <seglistitem> + <seg>10</seg> + <seg></seg> + <seg>Exam LPI-201</seg> + <seg></seg> + </seglistitem> + <seglistitem> + <seg>11</seg> + <seg></seg> + <seg>LPI-202 Course Day</seg> + <seg>9:30 - 17:30</seg> + </seglistitem> + <seglistitem> + <seg>12</seg> + <seg></seg> + <seg>LPI-202 Course Evening</seg> + <seg>18:30 - 22:30</seg> + </seglistitem> + <seglistitem> + <seg>13</seg> + <seg></seg> + <seg>Exam LPI-202</seg> + <seg></seg> + </seglistitem> + </segmentedlist> + </para> </appendix> + + <appendix id="LinuxSeniorManual-Appendix-CourseSchedule-OGD"> + <title>Course Schedule OGD Linux Senior Group 2008-2</title> + <para> + <segmentedlist> + <segtitle>Week #</segtitle> + <segtitle>Date</segtitle> + <segtitle>Day Description</segtitle> + <segtitle>Start / End</segtitle> + <seglistitem> + <seg>1</seg> + <seg>2008-09-03</seg> + <seg>Kickoff Meeting</seg> + <seg>18:30 - 20:30</seg> + </seglistitem> + <seglistitem> + <seg>2</seg> + <seg>2008-09-10</seg> + <seg>LPI-101 Course Day</seg> + <seg>9:30 - 17:30</seg> + </seglistitem> + <seglistitem> + <seg>3</seg> + <seg>2008-09-17</seg> + <seg>LPI-101 Course Evening</seg> + <seg>18:30 - 22:30</seg> + </seglistitem> + <seglistitem> + <seg>4</seg> + <seg>2008-09-24</seg> + <seg>Exam LPI-101</seg> + <seg></seg> + </seglistitem> + <seglistitem> + <seg>5</seg> + <seg>2008-10-01</seg> + <seg>LPI-102 Course Day</seg> + <seg>9:30 - 17:30</seg> + </seglistitem> + <seglistitem> + <seg>6</seg> + <seg>2008-10-08</seg> + <seg>LPI-202 Course Evening</seg> + <seg>18:30 - 22:30</seg> + </seglistitem> + <seglistitem> + <seg>7</seg> + <seg>2008-10-15</seg> + <seg>Exam LPI-102</seg> + <seg></seg> + </seglistitem> + <seglistitem> + <seg>8</seg> + <seg>2008-10-22</seg> + <seg>LPI-201 Course Day</seg> + <seg>9:30 - 17:30</seg> + </seglistitem> + <seglistitem> + <seg>9</seg> + <seg>2008-10-29</seg> + <seg>LPI-201 Course Evening</seg> + <seg>18:30 - 22:30</seg> + </seglistitem> + <seglistitem> + <seg>10</seg> + <seg>2008-11-5</seg> + <seg>Exam LPI-201</seg> + <seg></seg> + </seglistitem> + <seglistitem> + <seg>11</seg> + <seg>2008-11-12</seg> + <seg>LPI-202 Course Day</seg> + <seg>9:30 - 17:30</seg> + </seglistitem> + <seglistitem> + <seg>12</seg> + <seg>2008-11-19</seg> + <seg>LPI-202 Course Evening</seg> + <seg>18:30 - 22:30</seg> + </seglistitem> + <seglistitem> + <seg>13</seg> + <seg>2008-11-26</seg> + <seg>Exam LPI-202</seg> + <seg></seg> + </seglistitem> + </segmentedlist> + </para> + </appendix> + <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </part> diff --git a/en-US/Books/Linux/Senior/Manual.xml b/en-US/Books/Linux/Senior/Manual.xml index 67e304c..9efb08b 100644 --- a/en-US/Books/Linux/Senior/Manual.xml +++ b/en-US/Books/Linux/Senior/Manual.xml @@ -17,10 +17,10 @@ <section id="LinuxSeniorManual-CourseSchedule"> <title>Course Schedule</title> <para> - Appendix A has <ulink url="LinuxSeniorManual-Appendix-ExampleCourseSchedule.html">an example course schedule</ulink> getting students through the entire course (up to LPIC-2) in 12 weeks, excluding the kickoff meeting. For each exam, of which there are 4, students have one day and one evening, during which the teacher can layout some more details on a certain topic, is available for questions and can request the students exercise their new skills, then take the exam. + <xref linkend="LinuxSeniorManual-Appendix-ExampleCourseSchedule" /> is an example course schedule getting students through the entire course (up to LPIC-2) in 12 weeks, excluding the kickoff meeting. For each exam, of which there are 4, students have one day and one evening, during which the teacher can layout some more details on a certain topic, is available for questions and can request the students exercise their new skills, then take the exam. </para> <para> - This example course schedule has some of the details pre-entered for you. You can adjust this to reflect your course schedule, and hand it out to your students during the kickoff meeting, along with the <ulink url="LinuxSeniorCourse.html">Course material</ulink> for this course. + This example course schedule has some of the details pre-entered for you. You can adjust this to reflect your course schedule, and hand it out to your students during the kickoff meeting, along with the <link linkend="LinuxSeniorCourse">Course material</link> for this course. </para> </section> diff --git a/en-US/Courses.xml b/en-US/Courses.xml index 33aa63c..d5dd19e 100644 --- a/en-US/Courses.xml +++ b/en-US/Courses.xml @@ -78,6 +78,23 @@ See also: <xref linkend="LinuxSeniorManual" /> for teachers of the Linux Senior Course Track. </para> </listitem> + + </itemizedlist> </para> </formalpara> @@ -175,4 +192,10 @@ <xi:include href="Books/Linux/Senior/Manual.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </set> + <set> + <title>RHCE Training, Course Track</title> + <xi:include href="Books/Linux/RHCETraining/Course.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Books/Linux/RHCETraining/Manual.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + </set> + </set>

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

courses-commits September 2008