[system-administrators-guide] Markup and language, update some output
by stephenw
commit ac404713551a95349823f438ac349dec6f10df3c
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Thu Oct 23 21:42:03 2014 +0200
Markup and language, update some output
in en-US/Working_with_Kernel_Modules.xml
en-US/Working_with_Kernel_Modules.xml | 127 +++++++++++++++++----------------
1 files changed, 64 insertions(+), 63 deletions(-)
---
diff --git a/en-US/Working_with_Kernel_Modules.xml b/en-US/Working_with_Kernel_Modules.xml
index ad41096..790d15f 100644
--- a/en-US/Working_with_Kernel_Modules.xml
+++ b/en-US/Working_with_Kernel_Modules.xml
@@ -70,38 +70,36 @@
<screen>
~]$ <command>lsmod</command>
Module Size Used by
-xfs 803635 1
-exportfs 3424 1 xfs
-vfat 8216 1
-fat 43410 1 vfat
-tun 13014 2
-fuse 54749 2
-ip6table_filter 2743 0
-ip6_tables 16558 1 ip6table_filter
-ebtable_nat 1895 0
-ebtables 15186 1 ebtable_nat
-ipt_MASQUERADE 2208 6
-iptable_nat 5420 1
-nf_nat 19059 2 ipt_MASQUERADE,iptable_nat
-rfcomm 65122 4
-ipv6 267017 33
-sco 16204 2
-bridge 45753 0
-stp 1887 1 bridge
-llc 4557 2 bridge,stp
-bnep 15121 2
-l2cap 45185 16 rfcomm,bnep
-cpufreq_ondemand 8420 2
-acpi_cpufreq 7493 1
-freq_table 3851 2 cpufreq_ondemand,acpi_cpufreq
-usb_storage 44536 1
-sha256_generic 10023 2
-aes_x86_64 7654 5
-aes_generic 27012 1 aes_x86_64
-cbc 2793 1
-dm_crypt 10930 1
-kvm_intel 40311 0
-kvm 253162 1 kvm_intel
+tcp_lp 12663 0
+bnep 19704 2
+bluetooth 372662 7 bnep
+rfkill 26536 3 bluetooth
+fuse 87661 3
+ip6t_rpfilter 12546 1
+ip6t_REJECT 12939 2
+ipt_REJECT 12541 2
+xt_conntrack 12760 7
+ebtable_nat 12807 0
+ebtable_broute 12731 0
+bridge 110196 1 ebtable_broute
+stp 12976 1 bridge
+llc 14552 2 stp,bridge
+ebtable_filter 12827 0
+ebtables 30913 3 ebtable_broute,ebtable_nat,ebtable_filter
+ip6table_nat 13015 1
+nf_conntrack_ipv6 18738 5
+nf_defrag_ipv6 34651 1 nf_conntrack_ipv6
+nf_nat_ipv6 13279 1 ip6table_nat
+ip6table_mangle 12700 1
+ip6table_security 12710 1
+ip6table_raw 12683 1
+ip6table_filter 12815 1
+ip6_tables 27025 5 ip6table_filter,ip6table_mangle,ip6table_security,ip6table_nat,ip6table_raw
+iptable_nat 13011 1
+nf_conntrack_ipv4 14862 4
+nf_defrag_ipv4 12729 1 nf_conntrack_ipv4
+nf_nat_ipv4 13263 1 iptable_nat
+nf_nat 21798 4 nf_nat_ipv4,nf_nat_ipv6,ip6table_nat,iptable_nat
<lineannotation>[output truncated]</lineannotation></screen>
<para>Each row of <command>lsmod</command> output specifies:</para>
<itemizedlist>
@@ -140,7 +138,7 @@ kvm 253162 1 kvm_intel
<primary><command>modinfo</command></primary>
<seealso>kernel module</seealso>
</indexterm>
- <para>You can display detailed information about a kernel module by running the <command>modinfo <replaceable>module_name</replaceable></command> command.</para>
+ <para>You can display detailed information about a kernel module by running the <command>modinfo <replaceable>module_name</replaceable></command> command.</para>
<note
id="note-Module_names_do_not_end_in_.ko">
<title>Module names do not end in .ko</title>
@@ -178,8 +176,7 @@ parm: IntMode:Interrupt Mode (array of int)
parm: SmartPowerDownEnable:Enable PHY smart power down (array of int)
parm: KumeranLockLoss:Enable Kumeran lock loss workaround (array of int)
parm: WriteProtectNVM:Write-protect NVM [WARNING: disabling this can lead to corrupted NVM] (array of int)
-parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the CRC (array of int)
-</screen>
+parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the CRC (array of int)</screen>
</example>
<variablelist>
<para>Here are descriptions of a few of the fields in <command>modinfo</command> output:</para>
@@ -233,7 +230,7 @@ parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the
<screen>~]# <command>modinfo e1000e | grep "^parm" | sort</command>
parm: copybreak:Maximum size of packet that is copied to a new buffer on receive (uint)
parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the CRC (array of int)
-parm: EEE:Enable/disable on parts that support the feature (array of int)
+parm: debug:Debug level (0=none,...,16=all) (int)
parm: InterruptThrottleRate:Interrupt Throttling Rate (array of int)
parm: IntMode:Interrupt Mode (array of int)
parm: KumeranLockLoss:Enable Kumeran lock loss workaround (array of int)
@@ -285,12 +282,12 @@ parm: WriteProtectNVM:Write-protect NVM [WARNING: disabling this can l
<title>modprobe -v shows module dependencies as they are loaded</title>
<para>You can load the <systemitem class="protocol">Fibre Channel over Ethernet</systemitem> module verbosely by typing the following at a shell prompt:</para>
<screen>~]# <command>modprobe -v fcoe</command>
-insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/scsi_tgt.ko
-insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/scsi_transport_fc.ko
-insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/libfc/libfc.ko
-insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/fcoe/libfcoe.ko
-insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/fcoe/fcoe.ko</screen>
- <para>In this example, you can see that <command>modprobe</command> loaded the <systemitem class="resource">scsi_tgt</systemitem>, <systemitem class="resource">scsi_transport_fc</systemitem>, <systemitem class="resource">libfc</systemitem> and <systemitem class="resource">libfcoe</systemitem> modules as dependencies before finally loading <systemitem class="resource">fcoe</systemitem>. Also note that <command>modprobe</command> used the more <quote>primitive</quote> <command>insmod</command> command to insert the modules into the running kernel.</para>
+insmod /lib/modules/3.16.6-200.fc20.x86_64/kernel/drivers/scsi/scsi_tgt.ko
+insmod /lib/modules/3.16.6-200.fc20.x86_64/kernel/drivers/scsi/scsi_transport_fc.ko
+insmod /lib/modules/3.16.6-200.fc20.x86_64/kernel/drivers/scsi/libfc/libfc.ko
+insmod /lib/modules/3.16.6-200.fc20.x86_64/kernel/drivers/scsi/fcoe/libfcoe.ko
+insmod /lib/modules/3.16.6-200.fc20.x86_64/kernel/drivers/scsi/fcoe/fcoe.ko</screen>
+ <para>In this example, you can see that <command>modprobe</command> loaded the <systemitem class="resource">scsi_tgt</systemitem>, <systemitem class="resource">scsi_transport_fc</systemitem>, <systemitem class="resource">libfc</systemitem> and <systemitem class="resource">libfcoe</systemitem> modules as dependencies before finally loading <systemitem class="resource">fcoe</systemitem>. Also note that <command>modprobe</command> used the more primitive <command>insmod</command> command to insert the modules into the running kernel.</para>
</example>
<indexterm>
<primary>kernel module</primary>
@@ -344,20 +341,21 @@ insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/fcoe/fcoe.ko</scree
<para>See <xref linkend="sec-Listing_Currently-Loaded_Modules"/> for more information about using <command>lsmod</command> to obtain the names of the modules which are preventing you from unloading a certain module.</para>
<example id="ex-unloading_a_kernel_module">
<title>Unloading a kernel module</title>
- <para>For example, if you want to unload the <systemitem class="resource">firewire_ohci</systemitem> module (because you believe there is a bug in it that is affecting system stability, for example), your terminal session might look similar to this:</para>
+ <para>For example, if you want to unload the <systemitem class="resource">firewire_ohci</systemitem> module, your terminal session might look similar to this:</para>
<screen>~]# <command>modinfo -F depends firewire_ohci</command>
-depends: firewire-core
+firewire-core
~]# <command>modinfo -F depends firewire_core</command>
-depends: crc-itu-t
+crc-itu-t
~]# <command>modinfo -F depends crc-itu-t</command>
-depends:</screen>
+
+</screen>
<para>You have figured out the dependency tree (which does not branch in this example) for the loaded Firewire modules: <systemitem class="resource">firewire_ohci</systemitem> depends on <systemitem class="resource">firewire_core</systemitem>, which itself depends on <systemitem class="resource">crc-itu-t</systemitem>.</para>
<para>You can unload <systemitem class="resource">firewire_ohci</systemitem> using the <command>modprobe -v -r <replaceable>module_name</replaceable></command> command, where <option>-r</option> is short for <option>--remove</option> and <option>-v</option> for <option>--verbose</option>:</para>
<screen>~]# <command>modprobe -r -v firewire_ohci</command>
-rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/firewire/firewire-ohci.ko
-rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/firewire/firewire-core.ko
-rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/lib/crc-itu-t.ko</screen>
- <para>The output shows that modules are unloaded in the reverse order that they are loaded, given that no processes depend on any of the modules being unloaded.</para>
+rmmod firewire_ohci
+rmmod firewire_core
+rmmod crc_itu_t</screen>
+ <para>The output shows that modules are unloaded in the reverse order that they are loaded, given that no processes depend on any of the modules being unloaded.</para>
</example>
<indexterm>
<primary>kernel module</primary>
@@ -392,12 +390,18 @@ rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/lib/crc-itu-t.ko</screen>
<para>You can unload all dependencies of the module you want to set parameters for, unload the module using <command>modprobe -r</command>, and then load it with <command>modprobe</command> along with a list of customized parameters. This method is often used when the module does not have many dependencies, or to test different combinations of parameters without making them persistent, and is the method covered in this section.</para>
</listitem>
<listitem>
- <para>Alternatively, you can list the new parameters in an existing or newly-created file in the <filename>/etc/modprobe.d/</filename> directory. This method makes the module parameters persistent by ensuring that they are set each time the module is loaded, such as after every reboot or <command>modprobe</command> command. This method is covered in <xref
+ <para>Alternatively, you can list the new parameters in an existing or newly created file in the <filename>/etc/modprobe.d/</filename> directory. This method makes the module parameters persistent by ensuring that they are set each time the module is loaded, such as after every reboot or <command>modprobe</command> command. This method is covered in <xref
linkend="sec-Persistent_Module_Loading"/>, though the following information is a prerequisite.</para>
</listitem>
</orderedlist>
+ <example
+ id="ex-Supplying_optional_parameters_when_loading_a_kernel_module">
+ <title>Supplying optional parameters when loading a kernel module</title>
<para>You can use <command>modprobe</command> to load a kernel module with custom parameters using the following command line format:</para>
- <screen><command>modprobe <replaceable>module_name</replaceable> <optional><replaceable>parameter</replaceable>=<replaceable>value</replaceable></optional></command></screen>
+ <screen>~]# <command>modprobe <replaceable>module_name</replaceable> <optional><replaceable>parameter</replaceable>=<replaceable>value</replaceable></optional>
+ </command>
+ </screen>
+ </example>
<para>When loading a module with custom parameters on the command line, be aware of the following:</para>
<itemizedlist>
<listitem>
@@ -427,21 +431,18 @@ rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/lib/crc-itu-t.ko</screen>
<title>Loading a Kernel Module with Custom Parameters</title>
<step
id="proc-step1-Loading_a_Kernel_Module_with_Custom_Parameters">
- <para>First, ensure the module is not already loaded into the kernel. For example:</para>
- <screen>~]# <command>lsmod | grep e1000e</command>
-~]# </screen>
- <para>Output indicates that the module is already loaded into the kernel, in which case you must first unload it before proceeding. See <xref
+ <para>First, ensure the module is not already loaded into the kernel:</para>
+ <screen>~]# <command>lsmod |grep e1000e</command>
+~]# </screen>
+ <para>Output would indicate that the module is already loaded into the kernel, in which case you must first unload it before proceeding. See <xref
linkend="sec-Unloading_a_Module"/> for instructions on safely unloading it.</para>
</step>
<step
id="proc-step2-Loading_a_Kernel_Module_with_Custom_Parameters">
- <para>Load the module and list all custom parameters after the module name. For example, if you wanted to load the Intel PRO/1000 network driver with the interrupt throttle rate set to 3000 interrupts per second for the first, second and third instances of the driver, and Energy Efficient Ethernet (EEE) turned on<footnote
- id="footnote-Energy_Efficient_Ethernet"><para>Despite what the example might imply, Energy Efficient Ethernet is turned on by default in the <systemitem
- class="resource">e1000e</systemitem> driver.</para>
- </footnote>
-, you would run, as <systemitem class="username">root</systemitem>:</para>
- <screen>~]# <command>modprobe e1000e InterruptThrottleRate=3000,3000,3000 EEE=1</command></screen>
- <para>This example illustrates passing multiple valued to a single parameter by separating them with commas and omitting any spaces between them.</para>
+ <para>Load the module and list all custom parameters after the module name. For example, if you wanted to load the Intel PRO/1000 network driver with the interrupt throttle rate set to 3000 interrupts per second for the first, second, and third instances of the driver, and turn on debug, you would run, as <systemitem class="username">root</systemitem>:</para>
+ <screen>~]# <command>modprobe e1000e InterruptThrottleRate=3000,3000,3000 debug=1</command>
+ </screen>
+ <para>This example illustrates passing multiple values to a single parameter by separating them with commas and omitting any spaces between them.</para>
</step>
</procedure>
</section>
9 years, 6 months
[system-administrators-guide] Update: Persistent Module Loading
by stephenw
commit 15bd74a905f25da3fc6e773b0e8e1bd88e09c49f
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Thu Oct 23 21:41:18 2014 +0200
Update: Persistent Module Loading
Thank you David Shea
en-US/Working_with_Kernel_Modules.xml | 36 +++++++++++----------------------
1 files changed, 12 insertions(+), 24 deletions(-)
---
diff --git a/en-US/Working_with_Kernel_Modules.xml b/en-US/Working_with_Kernel_Modules.xml
index cbabb95..ad41096 100644
--- a/en-US/Working_with_Kernel_Modules.xml
+++ b/en-US/Working_with_Kernel_Modules.xml
@@ -459,32 +459,20 @@ rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/lib/crc-itu-t.ko</screen>
<tertiary><filename class="directory">/etc/sysconfig/modules/</filename></tertiary>
</indexterm>
<para>As shown in <xref
- linkend="ex-Listing_information_about_a_kernel_module_with_lsmod"/>, many kernel modules are loaded automatically at boot time. You can specify additional modules to be loaded by creating a new <filename><replaceable>file_name</replaceable>.modules</filename> file in the <filename class="directory">/etc/sysconfig/modules/</filename> directory, where <replaceable>file_name</replaceable> is any descriptive name of your choice. Your <filename><replaceable>file_name</replaceable>.modules</filename> files are treated by the system startup scripts as shell scripts, and as such should begin with an <firstterm>interpreter directive</firstterm> (also called a <quote>bang line</quote>) as their first line:</para>
- <programlisting language="Bash">#!/bin/sh</programlisting>
- <para>Additionally, the <filename><replaceable>file_name</replaceable>.modules</filename> file should be executable. You can make it executable by running:</para>
- <screen>modules]# <command>chmod +x <replaceable>file_name</replaceable>.modules</command>
- </screen>
+ linkend="ex-Listing_information_about_a_kernel_module_with_lsmod"/>, many kernel modules are loaded automatically at boot time. You can specify additional modules to be loaded by the <systemitem class="daemon">systemd-modules-load.service</systemitem> daemon by creating a <filename><replaceable>program</replaceable>.conf</filename> file in the <filename class="directory">/etc/modules-load.d/</filename> directory, where <replaceable>program</replaceable> is any descriptive name of your choice. The files in <filename class="directory">/etc/modules-load.d/</filename> are text files that list the modules to be loaded, one per line.</para>
<example
- id="ex-bluez-uinput.modules">
- <title>/etc/sysconfig/modules/bluez-uinput.modules</title>
- <para>The following <filename>bluez-uinput.modules</filename> script loads the <systemitem class="resource">uinput</systemitem> module:</para>
- <programlisting language="Bash">#!/bin/sh
-
-if [ ! -c /dev/input/uinput ] ; then
- exec /sbin/modprobe uinput >/dev/null 2>&1
-fi</programlisting>
- <para>The <literal>if</literal>-conditional statement on the third line ensures that the <filename>/dev/input/uinput</filename> file does <emphasis>not</emphasis> already exist (the <literal>!</literal> symbol negates the condition), and, if that is the case, loads the <systemitem
- class="resource">uinput</systemitem> module by calling <command>exec /sbin/modprobe uinput</command>. Note that the <systemitem
- class="resource">uinput</systemitem> module creates the <filename>/dev/input/uinput</filename> file, so testing to see if that file exists serves as verification of whether the <systemitem
- class="resource">uinput</systemitem> module is loaded into the kernel.</para>
- <para>The following <command>>/dev/null 2>&1</command> clause at the end of that line redirects any output to <filename>/dev/null</filename> so that the <command>modprobe</command> command remains quiet.</para>
+ id="ex-A_Text_File_to_Load_a_Module">
+ <title>A Text File to Load a Module</title>
+ <para>
+ To create a file to load the <filename>virtio-net.ko</filename> module, create a file <filename>/etc/modules-load.d/virtio-net.conf</filename> with the following content:
+ </para>
+ <screen># Load virtio-net.ko at boot
+virtio-net</screen>
</example>
- <!-- silas: most modules are autoloaded these days...
- <note
- id="note-No_Need_to_Load_Network_and_SCSI_Modules">
- <title>Note: Do Not Load Network and SCSI Modules</title>
- <para>Networking and SCSI modules do not generally need to be manually loaded as they have their own particular loading mechanisms.</para>
- </note>-->
+ <para>
+ See the <filename>modules-load.d(5)</filename> and <filename>systemd-modules-load.service(8)</filename> man pages for more information.
+ </para>
+
</section>
<section
9 years, 6 months
[system-administrators-guide] Improve markup for resources section
by stephenw
commit cfe4c6881bdae9d225ea10f7b3923385fd76b472
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Thu Oct 23 21:31:45 2014 +0200
Improve markup for resources section
in en-US/Working_with_Kernel_Modules.xml
en-US/Working_with_Kernel_Modules.xml | 107 +++++++++++++-------------------
1 files changed, 44 insertions(+), 63 deletions(-)
---
diff --git a/en-US/Working_with_Kernel_Modules.xml b/en-US/Working_with_Kernel_Modules.xml
index 3fb7b2b..cbabb95 100644
--- a/en-US/Working_with_Kernel_Modules.xml
+++ b/en-US/Working_with_Kernel_Modules.xml
@@ -491,69 +491,50 @@ fi</programlisting>
id="s1-kernel-modules-additional-resources">
<title>Additional Resources</title>
<para>For more information on kernel modules and their utilities, see the following resources.</para>
- <section id="s2-kernel-modules-additional-resources-installed">
- <title>Installed Documentation</title>
- <para>There are a number of manual pages for various utilities related to kernel modules:</para>
- <variablelist>
- <varlistentry>
- <term><command>man lsmod</command></term>
- <listitem>
- <para>The manual page for the <command>lsmod</command> command.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><command>man modinfo</command></term>
- <listitem>
- <para>The manual page for the <command>modinfo</command> command.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><command>man modprobe</command></term>
- <listitem>
- <para>The manual page for the <command>modprobe</command> command.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><command>man rmmod</command></term>
- <listitem>
- <para>The manual page for the <command>rmmod</command> command.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><command>man ethtool</command></term>
- <listitem>
- <para>The manual page for the <command>ethtool</command> command.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><command>man mii-tool</command></term>
- <listitem>
- <para>The manual page for the <command>mii-tool</command> command.</para>
- </listitem>
- </varlistentry>
- </variablelist>
- <para>Additionally, you can refer to the documentation provided by the <package>kernel-doc</package> package:</para>
- <variablelist>
- <varlistentry>
- <term><filename class="directory">/usr/share/doc/kernel-doc-<replaceable>kernel_version</replaceable>/Documentation/</filename></term>
- <listitem>
- <para>This directory contains information on the kernel, kernel modules, and their respective parameters. Note that before accessing the kernel documentation, you must run the following command as <systemitem class="username">root</systemitem>:</para>
- <screen><command>yum install kernel-doc</command></screen>
- </listitem>
- </varlistentry>
- </variablelist>
- </section>
- <section id="s2-kernel-modules-additional-resources-websites">
- <title>Useful Websites</title>
- <variablelist>
- <varlistentry>
- <term><ulink url="http://tldp.org/HOWTO/Module-HOWTO/">Linux Loadable Kernel Module HOWTO</ulink></term>
- <listitem>
- <para>The <citetitle>Linux Loadable Kernel Module HOWTO</citetitle> from the Linux Documentation Project contains further information on working with kernel modules.</para>
- </listitem>
- </varlistentry>
- </variablelist>
- </section>
+ <bridgehead
+ id="bh-Manual_Page_Documentation">Manual Page Documentation</bridgehead>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>lsmod(8)</filename> — The manual page for the <command>lsmod</command> command.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>modinfo(8)</filename> — The manual page for the <command>modinfo</command> command.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>modprobe(8)</filename> — The manual page for the <command>modprobe</command> command.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>rmmod(8)</filename> — The manual page for the <command>rmmod</command> command.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>ethtool(8)</filename> — The manual page for the <command>ethtool</command> command.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>mii-tool(8)</filename> — The manual page for the <command>mii-tool</command> command.</para>
+ </listitem>
+ </itemizedlist>
+ <bridgehead
+ id="bh-Installable_and_External_Documentation">Installable and External Documentation</bridgehead>
+ <itemizedlist>
+ <!--<listitem>
+ <para>
+ <filename
+ class="directory">/usr/share/doc/kernel-doc-<replaceable>kernel_version</replaceable>/Documentation/</filename> — This directory, which is provided by the <package>kernel-doc</package> package, contains information on the kernel, kernel modules, and their respective parameters. Before accessing the kernel documentation, you must run the following command as <systemitem class="username">root</systemitem>:</para>
+ <screen>~]# <command>yum install kernel-doc</command>
+ </screen>
+ </listitem>-->
+ <listitem>
+ <para>
+ <ulink
+ url="http://tldp.org/HOWTO/Module-HOWTO/">Linux Loadable Kernel Module HOWTO</ulink> — The <citetitle>Linux Loadable Kernel Module HOWTO</citetitle> from the Linux Documentation Project contains further information on working with kernel modules.</para>
+ </listitem>
+ </itemizedlist>
</section>
</chapter>
<!-- silas: entire section removed in favor of explaining how to use modinfo
9 years, 6 months
[release-notes] Added an entry for Apache Spark.
by Simon Clark
commit bf67895773b6e44b270a376914ee780956a6101a
Author: Simon Clark <simon.richard.clark(a)gmail.com>
Date: Thu Oct 23 11:43:46 2014 +0100
Added an entry for Apache Spark.
en-US/Cluster.xml | 17 +++++++++++++++++
1 files changed, 17 insertions(+), 0 deletions(-)
---
diff --git a/en-US/Cluster.xml b/en-US/Cluster.xml
index 1fd5d5d..b48826e 100644
--- a/en-US/Cluster.xml
+++ b/en-US/Cluster.xml
@@ -61,4 +61,21 @@
<para>For more information see:
<ulink url="http://pig.apache.org/" />.</para>
</section>
+ <section id="apache-spark">
+ <title>Apache Spark</title>
+ <para>Apache Spark is a fast and general engine for large-scale
+ data processing. It supports developing custom analytic
+ processing applications over large data sets or streaming data.
+ Because it has the capability to cache intermediate results in
+ cluster memory and schedule DAGs of computations, Spark
+ programs can run up to 100x faster than equivalent Hadoop
+ MapReduce jobs. Spark applications are easy to develop,
+ parallel, fast, and resilient to failure, and they can operate
+ on data from in-memory collections, local files, a
+ Hadoop-compatible filesystem, or from a variety of streaming
+ sources. Spark also includes libraries for distributed machine
+ learning and graph algorithms.</para>
+ <para>For more information see:
+ <ulink url="http://spark.apache.org/" />.</para>
+ </section>
</section>
9 years, 6 months
[release-notes] Corrected a typo
by Simon Clark
commit 659fb61ee20c348abd1733608575d9ea2bf279a2
Author: Simon Clark <simon.richard.clark(a)gmail.com>
Date: Thu Oct 23 10:58:51 2014 +0100
Corrected a typo
en-US/Cluster.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Cluster.xml b/en-US/Cluster.xml
index 901b2e6..1fd5d5d 100644
--- a/en-US/Cluster.xml
+++ b/en-US/Cluster.xml
@@ -53,7 +53,7 @@
analysis programs, coupled with infrastructure for evaluating
these programs. The salient property of Pig programs is that
their structure is amenable to substantial parallelization,
- which in turns enables them to handle very large data sets. At
+ which, in turn, enables them to handle very large data sets. At
the present time, Pig's infrastructure layer consists of a
compiler that produces sequences of Map-Reduce programs, for
which large-scale parallel implementations already exist (e.g.,
9 years, 6 months
[release-notes] Added an entry for Apache Pig.
by Simon Clark
commit 69144d76245f2b498f2b32575fa4701c35dd7d93
Author: Simon Clark <simon.richard.clark(a)gmail.com>
Date: Thu Oct 23 10:46:37 2014 +0100
Added an entry for Apache Pig.
en-US/Cluster.xml | 15 +++++++++++++++
1 files changed, 15 insertions(+), 0 deletions(-)
---
diff --git a/en-US/Cluster.xml b/en-US/Cluster.xml
index 4785c12..901b2e6 100644
--- a/en-US/Cluster.xml
+++ b/en-US/Cluster.xml
@@ -46,4 +46,19 @@
<para>For more information see
<ulink url="http://oozie.apache.org/" />.</para>
</section>
+ <section id="apache-pig">
+ <title>Apache Pig</title>
+ <para>Apache Pig is a platform for analyzing large data sets
+ that consists of a high-level language for expressing data
+ analysis programs, coupled with infrastructure for evaluating
+ these programs. The salient property of Pig programs is that
+ their structure is amenable to substantial parallelization,
+ which in turns enables them to handle very large data sets. At
+ the present time, Pig's infrastructure layer consists of a
+ compiler that produces sequences of Map-Reduce programs, for
+ which large-scale parallel implementations already exist (e.g.,
+ the Hadoop subproject).</para>
+ <para>For more information see:
+ <ulink url="http://pig.apache.org/" />.</para>
+ </section>
</section>
9 years, 6 months
[release-notes] Added entry for Apache Oozie
by Simon Clark
commit 5a9847dbce500a186cebbd045b17a648f57c59d5
Author: Simon Clark <simon.richard.clark(a)gmail.com>
Date: Wed Oct 22 21:05:17 2014 +0100
Added entry for Apache Oozie
en-US/Cluster.xml | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
---
diff --git a/en-US/Cluster.xml b/en-US/Cluster.xml
index 6bdc9b8..4785c12 100644
--- a/en-US/Cluster.xml
+++ b/en-US/Cluster.xml
@@ -35,4 +35,15 @@
<para>For more information see
<ulink url="http://mesos.apache.org/" />.</para>
</section>
+ <section id="apache-oozie">
+ <title>Apache Oozie</title>
+ <para>Apache Oozie is a workflow scheduler to manage Hadoop
+ jobs. It is integrated with the rest of the Hadoop stack and
+ supports several types of Hadoop jobs out of the box (such as
+ Java map-reduce, Streaming map-reduce, Pig, Hive, Sqoop and
+ Distcp) as well as system specific jobs (such as Java programs
+ and shell scripts).</para>
+ <para>For more information see
+ <ulink url="http://oozie.apache.org/" />.</para>
+ </section>
</section>
9 years, 6 months
[release-notes] Moved Apache Ambari entry from Database Servers to Cluster
by Simon Clark
commit 00556cceded826e94a8c124e8b661856f85544ca
Author: Simon Clark <simon.richard.clark(a)gmail.com>
Date: Wed Oct 22 19:54:22 2014 +0100
Moved Apache Ambari entry from Database Servers to Cluster
en-US/Cluster.xml | 10 ++++++++++
en-US/Database_Servers.xml | 10 ----------
2 files changed, 10 insertions(+), 10 deletions(-)
---
diff --git a/en-US/Cluster.xml b/en-US/Cluster.xml
index 72810b8..6bdc9b8 100644
--- a/en-US/Cluster.xml
+++ b/en-US/Cluster.xml
@@ -8,6 +8,16 @@
<section>
<title>Cluster</title>
<para />
+ <section id="apache-ambari">
+ <title>Apache Ambari</title>
+ <para>The Apache Ambari project is aimed at making Hadoop
+ management simpler by developing software for provisioning,
+ managing, and monitoring Apache Hadoop clusters. Ambari
+ provides an intuitive, easy-to-use Hadoop management web UI
+ backed by its RESTful APIs.</para>
+ <para>For more information see
+ <ulink url="http://ambari.apache.org/" />.</para>
+ </section>
<section id="apache-mesos">
<title>Apache Mesos</title>
<para>Apache Mesos is a cluster manager that provides efficient
diff --git a/en-US/Database_Servers.xml b/en-US/Database_Servers.xml
index 3c367d8..66c0b6f 100644
--- a/en-US/Database_Servers.xml
+++ b/en-US/Database_Servers.xml
@@ -22,16 +22,6 @@
<para>For more information see
<ulink url="https://accumulo.apache.org" />.</para>
</section>
- <section id="apache-ambari">
- <title>Apache Ambari</title>
- <para>The Apache Ambari project is aimed at making Hadoop
- management simpler by developing software for provisioning,
- managing, and monitoring Apache Hadoop clusters. Ambari
- provides an intuitive, easy-to-use Hadoop management web UI
- backed by its RESTful APIs.</para>
- <para>For more information see
- <ulink url="http://ambari.apache.org/" />.</para>
- </section>
<section id="apache-hbase">
<title>Apache HBase</title>
<para>Apache HBase is used when you need random, realtime
9 years, 6 months
[release-notes] Added new entry for Apache Mesos
by Simon Clark
commit 457ada201248e54e6e2427ee1d42acc328be50c3
Author: Simon Clark <simon.richard.clark(a)gmail.com>
Date: Tue Oct 21 23:09:22 2014 +0100
Added new entry for Apache Mesos
en-US/Cluster.xml | 27 +++++++++++++++++++++------
1 files changed, 21 insertions(+), 6 deletions(-)
---
diff --git a/en-US/Cluster.xml b/en-US/Cluster.xml
index 846f40a..72810b8 100644
--- a/en-US/Cluster.xml
+++ b/en-US/Cluster.xml
@@ -1,13 +1,28 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<?xml version='1.0' encoding='utf-8'?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+ "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"
+[
<!ENTITY % BOOK_ENTITIES SYSTEM "Release_Notes.ent">
%BOOK_ENTITIES;
]>
-
<section>
<title>Cluster</title>
<para />
-
+ <section id="apache-mesos">
+ <title>Apache Mesos</title>
+ <para>Apache Mesos is a cluster manager that provides efficient
+ resource isolation and sharing across distributed applications,
+ or frameworks. It abstracts CPU, memory, storage, and other
+ compute resources away from machines (physical or virtual),
+ enabling fault-tolerant and elastic distributed systems to
+ easily be built and run effectively. Apache Mesos is built
+ using the same principles as the Linux kernel, only at a
+ different level of abstraction. The Mesos kernel runs on every
+ machine and provides applications (e.g., Hadoop, Spark, Kafka,
+ Elastic Search) with API's for resource management and
+ scheduling across entire datacenter and cloud
+ environments.</para>
+ <para>For more information see
+ <ulink url="http://mesos.apache.org/" />.</para>
+ </section>
</section>
-
-
9 years, 6 months
[release-notes] Added new sub-section for Cluster under Sysadmin
by Simon Clark
commit 0f930487dfc73dcf48b191d5e3cb28b516eea707
Author: Simon Clark <simon.richard.clark(a)gmail.com>
Date: Tue Oct 21 22:49:00 2014 +0100
Added new sub-section for Cluster under Sysadmin
en-US/Cluster.xml | 13 +++++++++++++
en-US/Section-Sysadmin.xml | 3 +++
2 files changed, 16 insertions(+), 0 deletions(-)
---
diff --git a/en-US/Cluster.xml b/en-US/Cluster.xml
new file mode 100644
index 0000000..846f40a
--- /dev/null
+++ b/en-US/Cluster.xml
@@ -0,0 +1,13 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Release_Notes.ent">
+%BOOK_ENTITIES;
+]>
+
+<section>
+ <title>Cluster</title>
+ <para />
+
+</section>
+
+
diff --git a/en-US/Section-Sysadmin.xml b/en-US/Section-Sysadmin.xml
index 16d5ac5..8c11475 100644
--- a/en-US/Section-Sysadmin.xml
+++ b/en-US/Section-Sysadmin.xml
@@ -64,5 +64,8 @@
-->
<xi:include href="Monitoring.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+ <xi:include href="Cluster.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
</section>
9 years, 6 months