From f207b82a4ffcba90a35ae5b8cf07a1bd19e2be69 Mon Sep 17 00:00:00 2001 From: William Cohen Date: Tue, 4 Nov 2008 16:53:01 -0500 Subject: Edit install and cross compile sections. Include scripts to find rpms with yum. --- .../en-US/CrossInstrumenting.xml | 9 ++- .../en-US/Installation.xml | 68 ++++++++++++++-------- 2 files changed, 48 insertions(+), 29 deletions(-) (limited to 'doc/SystemTap_Beginners_Guide/en-US') diff --git a/doc/SystemTap_Beginners_Guide/en-US/CrossInstrumenting.xml b/doc/SystemTap_Beginners_Guide/en-US/CrossInstrumenting.xml index 6a91beab..a16e4f48 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/CrossInstrumenting.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/CrossInstrumenting.xml @@ -29,7 +29,7 @@ deploy SystemTap on all those systems. In some cases, this may be neither feasible nor desired to fully deploy SystemTap on those systems. For instance corporate policy may prohibit an administrator from - installing RPMs that proved debug information or compilers on specific + installing RPMs that provide compilers or debug information on specific machines, which will prevent the deployment of SystemTap. @@ -37,7 +37,7 @@ To work around this, you can resort to cross-instrumentation. Cross-instrumentation is the process of generating SystemTap instrumentation module from a SystemTap - script on one computer to be used on another machine. This process offers + script on one computer to be used on another computer. This process offers the following benefits: @@ -146,7 +146,7 @@ Determine the kernel running on each target system by running the by running uname -r on each - target system: + target system. @@ -187,8 +187,7 @@ - stap -r kernel_version - script -m + stap -r kernel_version script -m module_name diff --git a/doc/SystemTap_Beginners_Guide/en-US/Installation.xml b/doc/SystemTap_Beginners_Guide/en-US/Installation.xml index 2d5eb98b..f2c0cd92 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Installation.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Installation.xml @@ -29,8 +29,8 @@ Important Many users confuse -debuginfo with -debug. Remember that the deployment of SystemTap requires the installation of the - -debuginfo version of the kernel, not the - -debug version. + -debuginfo package of the kernel, not the + -debug version of the kernel.
@@ -46,7 +46,8 @@ Assuming that the computer system has been configured to use Red Hat - Network (RHN), the two rpms can be installed with yum install + Network (RHN) or yum is available, + the two rpms can be installed with yum install systemtap systemtap-runtime. Before you use SystemTap the additional kernel information will need to be installed as described in the following section. @@ -79,7 +80,8 @@ For example, if you wish to use SystemTap on kernel version - 2.6.18-53.el5, then you would need to download and + 2.6.18-53.el5 on an i686 machine, + then you would need to download and install the following RPMs: @@ -89,6 +91,17 @@ kernel-devel-2.6.18-53.1.13.el5.i686.rpm + + Important + + + The version and architecture of the -devel, + -debuginfo and + -debuginfo-common packages must match the kernel + you wish to probe with SystemTap exactly. + + + The script can be used by normal users to determine what supporting kernel RPMs need to be installed on the machine to use SystemTap with a particular kernel. The script run @@ -108,8 +121,9 @@ - If the computer has access to Red Hat Network (RHN) and the yum-utils - package is installed, the stapprep.sh script can be run + If the yum-utils package is installed on the computer and has access to + the yum repositories, + the stapprep.sh script can be run by root to download and install the needed kernel packages via yum and rpm commands. Thus, the system administrator should be able to install the needed RPMs with the @@ -123,21 +137,10 @@ rhel-debuginfo, but this could be changed. One could search the /etc/yum.repo.d/ directory for debuginfo repositories --> - - Important - - - The version and architecture of the -devel, - -debuginfo and - -debuginfo-common packages must match the kernel - you wish to probe with SystemTap exactly. - - - - If the yum repsitories are not accessible from the - machine, the following lines of bash script will generate the URL for - the Red Hat Enterprise Linux 5 debuginfo RPM directory: + If yum is not available on a Red Hat Enterprise Linux + 5 machine, the following lines of bash script will generate the URL for + the debuginfo RPM directory: @@ -148,10 +151,27 @@ echo "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/$releasever/en/os/$base" - The package RPMs can be downloaded on another machine then copied to the - machine. Once you have downloaded the packages and copied them to the - machine, install the RPMs by running rpm -ivh - package names. + If yum in not available on a Fedora system, the + following lines of bash script will generate the URL for the location to + find the needed kernel RPMs: + + + +echo -n "Enter nvr of kernel-debuginfo (e.g. 2.6.25-14.fc9.x86_64) " ; \ +read NVR; \ +BASE=`uname -m` ; \ +NVR=`echo $NVR | sed s/.$BASE//` ; \ +VERSION=`echo $NVR | awk -F- '{print $1}'` ; \ +RELEASE=`echo $NVR | awk -F- '{print $2}'` ; \ +echo "http://kojipkgs.fedoraproject.org/\ +packages/kernel/$VERSION/$RELEASE/$BASE/" + + + + The package RPMs can be manually downloaded and copied to the + machine. Once you have manually copied the packages to the + machine, install the RPMs by running rpm --force -ivh + package_names.
-- cgit