[deployment-guide/comm-rel: 260/727] Wrote a chapter introduction.

[Jaromir Hradilek]

commit 965080cca4c04821663d40b5dcca247d4f59d8f3
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Wed Aug 4 14:37:37 2010 +0200

    Wrote a chapter introduction.

 en-US/The_kdump_Crash_Recovery_Service.xml |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)
---
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index 4a14e29..e2cf2a7 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -3,6 +3,12 @@
 ]>
 <chapter id="ch-kdump">
   <title>The <systemitem class="service">kdump</systemitem> Crash Recovery Service</title>
+  <para>
+    <systemitem class="service">kdump</systemitem> is an advanced crash dumping mechanism. When enabled, the system is booted from the context of another kernel. This second kernel reserves a small amount of memory, and its only purpose is to capture the core dump image in case the system crashes. Since being able to analyze the core dump helps significantly to determine the exact cause of the system failure, it is strongly recommended to have this feature enabled.
+  </para>
+  <para>
+    This chapter explains how to configure, test, and use the <systemitem class="service">kdump</systemitem> service in &MAJOROS;, and provides a brief overview of how to analyze the resulting core dump using the <application>Crash</application> debugging utility.
+  </para>
   <section id="s1-kdump-configuration">
     <title>Configuring the <systemitem class="service">kdump</systemitem> Service</title>
     <note>