public inbox for linux-kernel@vger.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@dcs.ed.ac.uk
Subject: Re: linux-2.4.0-test11 and sysklogd-1.3-31
Date: Thu, 07 Dec 2000 10:46:09 +1100	[thread overview]
Message-ID: <1348.976146369@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 06 Dec 2000 17:24:58 CDT." <14894.48314.363938.770481@somanetworks.com>

On Wed, 6 Dec 2000 17:24:58 -0500 (EST), 
"Georg Nikodym" <georgn@somanetworks.com> wrote:
>sysklogd 1.3-31 no longer compiles using the latest headers in test11.
>
>Strictly speaking this isn't a kernel bug...
>
>sysklogd's ksym_mod.c includes <linux/module.h>

Speaking as the modutils maintainer and the person who added list.h to
module.h, sysklogd should *not* be including linux/module.h.  Linus has
spoken, it is an error for user space applications to include kernel
headers.  Even modutils does not include linux/module.h, instead it has
a portable (2.0 through 2.4) local definition of struct module.

ksym_mod.c is only present to try to decode oops reports in klogd.
klogd only handles some architectures, it often gets the oops decode
wrong and it destroys the log information that is needed by other oops
decoders.  IMNSHO ksymoops does a much better job of decoding the oops,
but I maintain ksymoops so I am just a little biased ;)

I would prefer to see the oops decoding completely removed from klogd.
The only justification for klogd converting the oops is to save users
from running ksymoops by hand.  I would not mind klogd capturing the
oops text, forking to run ksymoops then logging the ksymoops output.
Just as along as the original text was left alone and the ksymoops
output was obviously distinguished from real kernel output.

-
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  0:18 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 [this message]
2000-12-07 17:36   ` Georg Nikodym
2000-12-07 22:51     ` Keith Owens
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=1348.976146369@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=georgn@somanetworks.com \
    --cc=greg@wind.enjellic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@dcs.ed.ac.uk \
    /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