Re: [PATCH] Documentation: ksymoops should no longer be used to decode Oops messages

[Kalin KOZHUHAROV <kalin@thinrope.net>]

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/ <-+
|[ ______________________ ]|

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/