summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFrank Ch. Eigler <fche@elastic.org>2008-09-30 19:26:39 -0400
committerFrank Ch. Eigler <fche@elastic.org>2008-09-30 19:26:39 -0400
commitd90adf0dff664bfe6a7f9b7e6ba0e008ca261a40 (patch)
treea90624ef9f1e6ff5043ea5e2a51d9f7a10c1ea72
parentb586f21fc0dbd1e195ece774f02334589a10ddb1 (diff)
downloadsystemtap-steved-d90adf0dff664bfe6a7f9b7e6ba0e008ca261a40.tar.gz
systemtap-steved-d90adf0dff664bfe6a7f9b7e6ba0e008ca261a40.tar.xz
systemtap-steved-d90adf0dff664bfe6a7f9b7e6ba0e008ca261a40.zip
More README text tweaks for run options
-rw-r--r--README22
1 files changed, 11 insertions, 11 deletions
diff --git a/README b/README
index 13b3aa5f..b7434256 100644
--- a/README
+++ b/README
@@ -10,10 +10,10 @@ See the INSTALL file for generic build instructions.
Prerequisites:
- linux kernel with kprobes (mainline 2.6.11+ or backport)
-- kernel module build environment (kernel-devel or kernel-smp-devel rpm)
+- kernel module build environment (kernel-devel rpm)
- kernel debugging information (kernel-debuginfo rpm)
- C compiler (same as what kernel was compiled with)
-- elfutils with libdwfl for debugging informatin parsing
+- elfutils with libdwfl for debugging information parsing
- root privileges
Installation steps:
@@ -61,21 +61,21 @@ Build steps:
- Run systemtap:
- To run the full test suite from the build tree.
- % sudo make installcheck
-
To run systemtap after installation, add $prefix/bin to your $PATH, or
refer to $prefix/bin/stap directly. If you keep your build tree
around, you can also use the "stap" binary there.
Some samples should be available under $prefix/share/doc/systemtap/examples.
- Normally, run "stap" as root.
- If desired, create "stapdev" and "stapusr" entries in /etc/groups.
- Any users in "stapdev" will be able to run systemtap as if with root
- privileges. Users in "stapusr" can only launch (with "staprun")
- pre-compiled probe modules (created by "stap -p4 ...") that a system
- administrator copied under /lib/modules/`uname -r`/systemtap.
+ Normally, run "stap" as root. If desired, create "stapdev" and
+ "stapusr" entries in /etc/groups. Any users in "stapdev" will be
+ able to run systemtap as if with root privileges. Users in "stapusr"
+ can only launch (with "staprun") pre-compiled probe modules (created
+ by "stap -p4 ...") that a system administrator copied under
+ /lib/modules/`uname -r`/systemtap.
+
+ To run the full test suite from the build tree.
+ % sudo make installcheck
Tips: