From: Axel Siebenwirth <axel@hh59.org>
To: linux-kernel@vger.kernel.org
Subject: Re: LKCD/kmsgdump for 2.5?
Date: Tue, 30 Jul 2002 19:10:27 +0200 [thread overview]
Message-ID: <20020730171027.GA278@prester.freenet.de> (raw)
In-Reply-To: <20020730153523.GA9238@alpha.home.local>
Hi!
On Tue, 30 Jul 2002, Willy Tarreau wrote:
> On Tue, Jul 30, 2002 at 04:23:05PM +0200, Axel Siebenwirth wrote:
> > Hi,
> >
> > I'm tired of handcopying my oopses. I read of something like LKCD and
> > kmsgdump but then I saw that these are only available for 2.4. But wouldn't
> > something like that be more useful for a development kernel as 2.5?
>
> of course, you're right. In my case, it's simply because I never
> compiled a 2.5 kernel yet. I may port kmsgdump to 2.5 if it doesn't
> take too much time.
Wouldn't it be wonderful to have something like that in development kernels
officially? That way more people could easily help debug the whole thing. Or
maybe just an officially maintained patch to current development kernels.
Regards,
Axel
prev parent reply other threads:[~2002-07-30 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 14:23 LKCD/kmsgdump for 2.5? Axel Siebenwirth
2002-07-30 15:35 ` Willy Tarreau
2002-07-30 17:10 ` Axel Siebenwirth [this message]
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=20020730171027.GA278@prester.freenet.de \
--to=axel@hh59.org \
--cc=linux-kernel@vger.kernel.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