[deployment-guide/comm-rel: 572/727] Moved a couple of admonitions a bit.

Jaromir Hradilek jhradile at fedoraproject.org
Tue Oct 19 13:13:05 UTC 2010


commit 0d69d1bacb236985d2930373ea6c1b57649a0318
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Fri Sep 3 13:42:59 2010 +0200

    Moved a couple of admonitions a bit.
    
    This won't affect the translation in any way, I am merely following
    Florian's recommendation.

 en-US/The_kdump_Crash_Recovery_Service.xml |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)
---
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index ac7cc16..6f2280c 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -11,6 +11,9 @@
   </para>
   <section id="s1-kdump-configuration">
     <title>Configuring the <systemitem class="service">kdump</systemitem> Service</title>
+    <para>
+      This section covers three common means of configuring the <systemitem class="service">kdump</systemitem> service: at the first boot, using the <application>Kernel Dump Configuration</application> graphical utility, and doing so manually on the command line. It also describes how to test the configuration to verify that everything works as expected.
+    </para>
     <indexterm>
       <primary><systemitem class="service">kdump</systemitem></primary>
       <secondary>system requirements</secondary>
@@ -21,9 +24,6 @@
         To use the <systemitem class="service">kdump</systemitem> service, you must have the <package>kexec-tools</package> package installed. Refer to <xref linkend="sec-Installing" /> for more information on how to install new packages in &MAJOROS;.
       </para>
     </note>
-    <para>
-      This section covers three common means of configuring the <systemitem class="service">kdump</systemitem> service: at the first boot, using the <application>Kernel Dump Configuration</application> graphical utility, and doing so manually on the command line. It also describes how to test the configuration to verify that everything works as expected.
-    </para>
     <section id="s2-kdump-configuration-firstboot">
       <title>Configuring the <systemitem class="service">kdump</systemitem> at First Boot</title>
       <para>
@@ -564,6 +564,9 @@ Kdump is operational</screen>
       <secondary>analyzing the dump</secondary>
       <see><application>crash</application></see>
     </indexterm>
+    <para>
+      To determine the cause of the system crash, you can use the <application>crash</application> utility. This utility allows you to interactively analyze a running Linux system as well as a core dump created by <systemitem>netdump</systemitem>, <systemitem>diskdump</systemitem>, <systemitem>xendump</systemitem>, or <systemitem>kdump</systemitem>. When started, it presents you with an interactive prompt very similar to the GNU Debugger (GDB).
+    </para>
     <indexterm>
       <primary><application>crash</application></primary>
       <secondary>system requirements</secondary>
@@ -578,9 +581,6 @@ Kdump is operational</screen>
         Refer to <xref linkend="sec-Installing" /> for more information on how to install new packages in &MAJOROS;.
       </para>
     </note>
-    <para>
-      To determine the cause of the system crash, you can use the <application>crash</application> utility. This utility allows you to interactively analyze a running Linux system as well as a core dump created by <systemitem>netdump</systemitem>, <systemitem>diskdump</systemitem>, <systemitem>xendump</systemitem>, or <systemitem>kdump</systemitem>. When started, it presents you with an interactive prompt very similar to the GNU Debugger (GDB).
-    </para>
     <indexterm>
       <primary><application>crash</application></primary>
       <secondary>opening the dump image</secondary>


More information about the docs-commits mailing list