All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: georgn@somanetworks.com
Cc: linux-kernel@vger.kernel.org, greg@wind.enjellic.com, sct@redhat.com
Subject: Re: linux-2.4.0-test11 and sysklogd-1.3-31
Date: Fri, 08 Dec 2000 09:51:48 +1100	[thread overview]
Message-ID: <5597.976229508@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Thu, 07 Dec 2000 12:36:01 CDT." <14895.51841.431444.405949@somanetworks.com>

On Thu, 7 Dec 2000 12:36:01 -0500 (EST), 
"Georg Nikodym" <georgn@somanetworks.com> wrote:
>>>>>> "KO" == Keith Owens <kaos@ocs.com.au> writes:
>
> KO> I would prefer to see the oops decoding completely removed from
> KO> klogd.
>
>Since nobody else has weighed in on this issue, I quickly did the
>necessary to effect Keith's suggestion.  What follows is a patch to
>sysklogd-1.3-31 (which after applying, ksym_mod.c can be removed):

You only removed the module symbol handling.  The problem is that the
entire klogd oops handling is out of date and broken.  I recommend
removing all oops processing from klogd, which means that klogd does
not need any symbols nor System.map.

-
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/

  reply	other threads:[~2000-12-07 23:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-06 22:24 linux-2.4.0-test11 and sysklogd-1.3-31 Georg Nikodym
2000-12-06 23:46 ` Keith Owens
2000-12-07 17:36   ` Georg Nikodym
2000-12-07 22:51     ` Keith Owens [this message]
2000-12-08 16:30       ` Georg Nikodym
2000-12-08 22:16         ` Keith Owens
2000-12-12  1:13           ` Georg Nikodym
2000-12-12  1:29             ` Georg Nikodym
2000-12-12  1:30             ` Keith Owens
2000-12-12  1:53               ` Georg Nikodym
2000-12-12  3:57                 ` Peter Samuelson

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=5597.976229508@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=georgn@somanetworks.com \
    --cc=greg@wind.enjellic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.