From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: ksymoops should no longer be used to decode Oops messages
Date: Fri, 07 Oct 2005 00:49:48 +0900 [thread overview]
Message-ID: <di3h5d$f82$1@sea.gmane.org> (raw)
In-Reply-To: <200510052239.43492.jesper.juhl@gmail.com>
Jesper Juhl wrote:
> Document the fact that ksymoops should no longer be used to decode Oops
> messages.
>
>
> Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
> ---
>
> Documentation/Changes | 7 +++----
> 1 files changed, 3 insertions(+), 4 deletions(-)
>
> --- linux-2.6.14-rc3-git5-orig/Documentation/Changes 2005-10-03 21:54:50.000000000 +0200
> +++ linux-2.6.14-rc3-git5/Documentation/Changes 2005-10-05 22:35:44.000000000 +0200
> @@ -31,7 +31,7 @@
> Eine deutsche Version dieser Datei finden Sie unter
> <http://www.stefan-winter.de/Changes-2.4.0.txt>.
>
> -Last updated: October 29th, 2002
> +Last updated: October 05th, 2005
>
> Chris Ricker (kaboom@gatech.edu or chris.ricker@genetics.utah.edu).
>
> @@ -139,9 +139,8 @@
> Ksymoops
> --------
>
> -If the unthinkable happens and your kernel oopses, you'll need a 2.4
> -version of ksymoops to decode the report; see REPORTING-BUGS in the
> -root of the Linux source for more information.
> +With a 2.4 kernel you need ksymoops to decode a kernel Oops message. With
> +2.6 kernels ksymoops is no longer needed and should not be used.
>
> Module-Init-Tools
> -----------------
OK, but what should I use then with 2.6??
And since when is ksymoops not usable with it?
I have reported quite a few times here, alaways with 2.6.x and nobody said anything about it...
Kalin.
--
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
next prev parent reply other threads:[~2005-10-06 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 20:39 Jesper Juhl
2005-10-05 21:28 ` Alexey Dobriyan
2005-10-05 21:28 ` Jesper Juhl
2005-10-06 15:49 ` Kalin KOZHUHAROV [this message]
2005-10-06 15:59 ` Randy.Dunlap
2005-10-06 16:09 ` Jesper Juhl
2005-10-06 16:48 ` Alexey Dobriyan
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='di3h5d$f82$1@sea.gmane.org' \
--to=kalin@thinrope.net \
--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
Powered by JetHome