lkml.org 
[lkml]   [2000]   [Dec]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: linux-2.4.0-test11 and sysklogd-1.3-31
>>>>> "KO" == Keith Owens <kaos@ocs.com.au> writes:

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

You're right.

My goal was to quickly get our build working again. I had no
expectation that anybody else on the planet would give a crap about my
patch...

But since you seem to and while we're doing extreme surgery, why have
klogd at all? Every other unix, kernel messages are handled by the
syslog system. What problem did klogd solve and does that problem
still exist today? Stated differently, aren't you just proposing to
reduce klogd to:

cat < /proc/kmsg > /dev/log &

(I know that this won't work on my box, but you get the idea)

Anyway, I'll look into simplifying klogd as you suggest...
-
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/

\
 
 \ /
  Last update: 2005-03-22 12:51    [W:0.110 / U:1.580 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site