From: Keith Owens <kaos@ocs.com.au>
To: Guennadi Liakhovetski <g.liakhovetski@ragingbull.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kdb for modules
Date: Tue, 09 Jan 2001 01:54:24 +1100 [thread overview]
Message-ID: <1415.978965664@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Mon, 08 Jan 2001 10:57:32 -0000." <Pine.GSO.4.21.0101081053210.25031-100000@acms23>
On Mon, 8 Jan 2001 10:57:32 +0000 (GMT),
Guennadi Liakhovetski <g.liakhovetski@ragingbull.com> wrote:
>Keith Owens wrote
>> kdb v0.6 is out of date and no longer supported. kdb v1.5 against
>> 2.2.18 is in ftp://oss.sgi.com/projects/kdb/download/ix86/, it supports
>> modules correctly. This patch is only there as a courtesy, SGI do not
>> support kdb on 2.2 kernels, all our debugging work is on 2.4 kernels.
>> If you want to use kdb on 2.2 kernels, you are pretty much on your own.
>
>Ok, this is fine, but just one question, please: is
>kdb-v1.5-2.2.18-pre15.gz going (or at least supposed to) work with 2.2.18
>(final)?
The only obvious difference between 2.2.18-pre15 and 2.2.18 that
affects kdb is a change to the sysctl numbers. I have put
kdb-v1.5-2.2.18.gz in http://oss.sgi.com/projects/kdb/download/ix86/.
Warning: I have not even compiled this patch, let alone tested it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-08 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 10:57 Kdb for modules Guennadi Liakhovetski
2001-01-08 14:54 ` Keith Owens [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-07 13:31 Sourav Sen
2001-01-07 13:49 ` Keith Owens
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=1415.978965664@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=g.liakhovetski@ragingbull.com \
--cc=linux-kernel@vger.kernel.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