From 4125a78ae5fc99abb8606bf0eda2a08b3e2d300c Mon Sep 17 00:00:00 2001
From: ddomingo <ddomingo@redhat.com>
Date: Thu, 2 Oct 2008 23:07:01 +1000
Subject: new section, iotop.stp

---
 doc/SystemTap_Beginners_Guide/en-US/CrossInstrumenting.xml | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

(limited to 'doc/SystemTap_Beginners_Guide/en-US/CrossInstrumenting.xml')

diff --git a/doc/SystemTap_Beginners_Guide/en-US/CrossInstrumenting.xml b/doc/SystemTap_Beginners_Guide/en-US/CrossInstrumenting.xml
index 07280100..cc451ec4 100644
--- a/doc/SystemTap_Beginners_Guide/en-US/CrossInstrumenting.xml
+++ b/doc/SystemTap_Beginners_Guide/en-US/CrossInstrumenting.xml
@@ -77,7 +77,7 @@
 	<title>Configuring a Host System and Target Systems</title>
 	
 <step>
-		<para>Configure <command>yum</command> on the <emphasis>host system</emphasis> to point to a repository containing the necessary debug RPMs for the <emphasis>target kernels</emphasis>. The following <command>yum</command> repository file (which you can add to <filename>/etc/yum.repos.d/</filename> points to a popular debug RPM repository for Red Hat Enterprise Linux 5:</para>
+		<para>Configure <command>yum</command> on the <emphasis>host system</emphasis> to point to a repository containing the necessary debug RPMs for the <emphasis>target kernels</emphasis>. The following <command>yum</command> repository file (which you can add to <filename>/etc/yum.repos.d/</filename> points to a popular debug RPM repository for i386 systems running Red Hat Enterprise Linux 5:</para>
 <screen>
 [rhel-debuginfo]
 name=Red Hat Enterprise Linux $releasever - $basearch - Debug
@@ -119,10 +119,11 @@ enabled=1
 
 <note>
 	<title>Note</title>
-	<para>To determine the version of a running kernel, run <command>uname -r</command>. To determine the architecture notation of a running kernel, run <command>uname -m</command>.</para>
+	<para>To determine the architecture notation of a running kernel, run <command>uname -m</command>.</para>
+<!--	<para>To determine the version of a running kernel, run <command>uname -r</command>. To determine the architecture notation of a running kernel, run <command>uname -m</command>.</para>-->
 </note>	
 
-<para>Once the the <emphasis>instrumentation module</emphasis>is compiled, copy it to the <emphasis>target system</emphasis> and load it using:</para>
+<para>Once the the <emphasis>instrumentation module</emphasis> is compiled, copy it to the <emphasis>target system</emphasis> and load it using:</para>
 
 <para><command>staprun <replaceable>instrumentation</replaceable></command></para>
 
@@ -142,6 +143,9 @@ enabled=1
 <step>
 	<para>Note the version of the target system's kernel on which you wish to use SystemTap. You can do this by logging onto the target system and running <command>uname -r</command> (assuming the system is running the kernel on which you wish to use SystemTap), or by inspecting <filename>/boot</filename>.</para>
 </step>	-->
-		
+<important>
+	<title>Important</title>
+	<para>The <emphasis>host system</emphasis> must be the same architecture as the <emphasis>target system</emphasis> in order for the <emphasis>instrumentation module</emphasis> to work.</para>
+</important>	
 
 	</section>	
\ No newline at end of file
-- 
cgit