From: Jesper Juhl <jesper.juhl@gmail.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org, Chris Ricker <kaboom@gatech.edu>,
chris.ricker@genetics.utah.edu,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] Documentation: ksymoops should no longer be used to decode Oops messages
Date: Wed, 5 Oct 2005 23:28:22 +0200 [thread overview]
Message-ID: <200510052328.22969.jesper.juhl@gmail.com> (raw)
In-Reply-To: <20051005212850.GD27229@mipter.zuzino.mipt.ru>
On Wednesday 05 October 2005 23:28, Alexey Dobriyan wrote:
> On Wed, Oct 05, 2005 at 10:39:43PM +0200, Jesper Juhl wrote:
> > Document the fact that ksymoops should no longer be used to decode Oops
> > messages.
>
> If it's considered harmful, better remove all references to ksymoops.
> 2.4 users will happily grab their copy of this file from 2.4 tree.
>
I opted to keep the entry but make an explicit note that ksymoops should not
be used for 2.6 kernels to make it clear. There are still people who use
ksymoops on 2.6 Oops messages, so I thought it would make sense to keep the
entry but make it clear that you should /not/ do that.
But, I'm fine with removing it as well.
> > 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.
>
Here's a patch to remove the Ksymoops entry instead.
I'll leave it up to the powers that be to sprinkle holy penguin pee on the
preferred version.
Ksymoops should not be used on 2.6 Oops messages, so remove the ksymoops entry
from Documentation/Changes
Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
---
Documentation/Changes | 9 +--------
1 files changed, 1 insertion(+), 8 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 23:21:45.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).
@@ -136,13 +136,6 @@
types, have a fdformat which works with 2.4 kernels, and similar goodies.
You'll probably want to upgrade.
-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.
-
Module-Init-Tools
-----------------
next prev parent reply other threads:[~2005-10-05 21:25 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 [this message]
2005-10-06 15:49 ` Kalin KOZHUHAROV
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=200510052328.22969.jesper.juhl@gmail.com \
--to=jesper.juhl@gmail.com \
--cc=adobriyan@gmail.com \
--cc=chris.ricker@genetics.utah.edu \
--cc=kaboom@gatech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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