From: William Cohen <wcohen@redhat.com>
To: David Smith <dsmith@redhat.com>
Cc: SystemTAP <systemtap@sources.redhat.com>
Subject: Re: Simple script to grab and install the appropriate kernel RPMs
Date: Tue, 04 Nov 2008 15:58:00 -0000 [thread overview]
Message-ID: <491070EE.2040901@redhat.com> (raw)
In-Reply-To: <49106DAD.2010105@redhat.com>
David Smith wrote:
> William Cohen wrote:
>> Hi All,
>>
>> In an effort to make it a bit easier to install systemtap on RHEL
>> machines, I have made a small script to figure out which RPMs to install
>> based either on the running kernel (no arguments to script) or the
>> output of "uname -r" as an argument to the script. This script is only
>> designed to work on RHEL. I would like to comments on it. The plan is to
>> include this in the Systemtap beginners guide to make it easier for
>> people to machine setup to run systemtap.
>
> Here's the script I've used for awhile now (as you'll see since it
> supports releases back to FC5). It isn't much different than your
> script, except it also supports Fedora. Note that it currently doesn't
> handle PAE kernels, but it could be made to handle that.
>
Thanks, David for the script. Did you try to use the yum_kdebug.sh script for
cross compiling examples? I noticed when trying to use "yum install" that yum
would complain about installing kernels older than the currently installed kernel.
I would like to revise the stapprep.sh scrip to handle fedora repos correctly.
There is the DEBUGINFOREPO variable that should be set appropriate for the
various fedoras.
-Will
next prev parent reply other threads:[~2008-11-04 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 19:14 William Cohen
2008-11-04 6:57 ` K.Prasad
2008-11-04 15:49 ` William Cohen
2008-11-04 15:44 ` David Smith
2008-11-04 15:58 ` William Cohen [this message]
2008-11-04 16:13 ` David Smith
2008-11-04 18:35 ` William Cohen
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=491070EE.2040901@redhat.com \
--to=wcohen@redhat.com \
--cc=dsmith@redhat.com \
--cc=systemtap@sources.redhat.com \
/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).