From: fche@redhat.com (Frank Ch. Eigler)
To: mglt.biz@gmail.com
Cc: systemtap@sourceware.org
Subject: Re: Comments on Installation Guide
Date: Sun, 05 Jun 2011 11:19:00 -0000 [thread overview]
Message-ID: <y0my61g34s0.fsf@fche.csb> (raw)
In-Reply-To: <4DE5EB4C.1020305@gmail.com> (Daniel Migault's message of "Wed, 01 Jun 2011 09:33:32 +0200")
Hi, Daniel -
mglt.biz wrote:
> I went through the documentation, and maybe I would add a few
> indications for the installation. It looks that some of them have
> been removed from previous installation guides.
Such distribution-specific information could go into the wiki, or
perhaps new README.fedora type files. Note that the main README
already has similar information.
> I Install systemtap
>
> If you want to install systemtap from rpm :
> yum install systemtap systemtap-client systemtap-grapher
> systemtap-runtime systemtap-sdt-devel systemtap-server
> systemtap-testsuite
The basic requirement is only systemtap and systemtap-runtime.
> If you want the latest version, then you may built it from the git
> repository :
> I.1. Download the git directory
> If you don't already have a local copy :
> git clone [...]
(Already in the README.)
> I.2. Get pre-requisit rpms :
> yum install xmlto [...]
"yum-builddep systemtap" should work about as well as that list.
> I.3. Configure and build :
> cd systemtap.git
> ./configure
> [...]
(Already in README.)
> II Configure your kernel :
>
> yum install kernel-devel-`uname -r`
> debuginfo-install kernel-`uname -r`
> [...]
These could be added to the README.
Hm, how about posting a proposed patch for the README file
for the couple of items that are missing?
- FChE
next prev parent reply other threads:[~2011-06-05 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 7:33 Daniel Migault
2011-06-05 11:19 ` Frank Ch. Eigler [this message]
2011-07-04 8:57 ` Daniel Migault
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=y0my61g34s0.fsf@fche.csb \
--to=fche@redhat.com \
--cc=mglt.biz@gmail.com \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).