From: William Cohen <wcohen@redhat.com>
To: Mike Mason <mmlnx@us.ibm.com>
Cc: SystemTAP <systemtap@sources.redhat.com>
Subject: Re: Fedora 7 based Systemtap LiveCD for i686 machines
Date: Mon, 11 Jun 2007 19:44:00 -0000 [thread overview]
Message-ID: <466DA610.5020705@redhat.com> (raw)
In-Reply-To: <466D9DE3.9090303@us.ibm.com>
Mike Mason wrote:
> Moving this thread to the systemtap list...
>
> William Cohen wrote:
>> Mike Mason wrote:
>>> Hi Will,
>>>
>>> I tried the live CD on another Windows-only laptop and had no
>>> problems rebooting back to Windows. I did it several times. I guess
>>> we shouldn't worry about it for now.
>>
>> Hmmm. All the machine I have are dual boot, so I can't verify this
>> problem. I guess we won't worry about this.
>
> For those new to this thread, I had a problem a couple times when I ran
> a live CD on a Windows-only system. The live CD ran fine, but I
> couldn't boot back to Windows. However, my latest test worked fine.
> We've had no problems with linux-only and dual-boot systems. We've
> decided not to worry about this for now. It's not clear it's a real
> problem. Plus it's unlikely OLS attendees will bring Windows-only laptops.
>
>>
>>> I noticed that the sockets tapset doesn't contain the fix I made that
>>> allows it to work with later kernels. If we can't include a later
>>> systemtap rpm, then I'll just update socket.stp with my examples
>>> rpm. Does that sound okay? I'll also probably install the
>>> tutorial-specific examples under /usr/share/doc/systemtap-0.5.13.
>>> I'd like to get people used to looking there.
>>
>> Yes, just be sure to have an example that works. We can put all the
>> examples together in an rpm.
>
> Will do.
>
>>
>>>
>>> I was going to ask if we could include the kernel source and cscope,
>>> but I realize that's out of the question. The kernel source alone is
>>> 437 MB!
>>>
>>> Regards,
>>> Mike
>>
>> The source is already in the debuginfo rpm. However, I don't know
>> about getting the cscope information in there. It isn't in an rpm.
>> Generating the stuff on the fly probably won't work too well either.
>
> I don't see any source coming from the debuginfo rpm. Where is it located?
What I said wasn't quite true. The .c and .h files are around. However, the make
and script files are not there. Take a look in /usr/src/debug/kernel-2.6.21 (or
similar directory).
-Will
next prev parent reply other threads:[~2007-06-11 19:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 22:02 William Cohen
2007-06-08 18:53 ` William Cohen
2007-06-10 15:45 ` Frank Ch. Eigler
[not found] ` <4669D266.6090304@us.ibm.com>
[not found] ` <466AB438.40506@redhat.com>
[not found] ` <466D9119.6080702@us.ibm.com>
[not found] ` <466D99BB.7070502@redhat.com>
2007-06-11 19:09 ` Mike Mason
2007-06-11 19:44 ` William Cohen [this message]
2007-06-11 20:04 ` Mike Mason
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=466DA610.5020705@redhat.com \
--to=wcohen@redhat.com \
--cc=mmlnx@us.ibm.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).