From: "Matt D. Robinson" <yakker@alacritech.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Hiro Yoshioka <hyoshiok@miraclelinux.com>,
lkcd-general@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [lkcd-general] Re: status of LKCD into Linux Kernel
Date: Wed, 13 Feb 2002 22:33:18 -0800 [thread overview]
Message-ID: <3C6B5A2E.2C2637C7@alacritech.com> (raw)
In-Reply-To: <20020214114457A.hyoshiok@miraclelinux.com> <3C6B51AA.6EB614C3@mandrakesoft.com>
A lot of progress has been made ...
LKCD is currently up to 2.4.17, and should be simple to
move into 2.5.
I've asked Linus and others for inclusion in the past, and I
think it deserves consideration for 2.5, especially now that it
can be built into the kernel without having to be turned on.
At least in those cases, people who want it can turn it on,
and those that don't will never see it.
The LKCD development team (over 10 engineers now) is ready.
--Matt
Jeff Garzik wrote:
>
> Hiro Yoshioka wrote:
> > I have a naive question. Will the LKCD be merged into
> > the Linus' kernel? If yes, when? wild guess?
>
> I talked with Matt Robinson(sp?) at LinuxWorld-NY about LKCD for a few
> minutes... he gave me the impression that a lot of progress has been
> made recently. IBM apparently has some guys working on it, too.
>
> I've always thought Linux needs industrial strength crash dumps like the
> other Unices. There are many benefits, but my own is self interest:
> bug reports get 1000 times better, since you get along with the crash
> point a lot more info about the state of the system at the time of the
> crash.
>
> So, I hope LKCD is looked upon favorably by the Penguin Gods. :)
>
> Jeff
next prev parent reply other threads:[~2002-02-14 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 2:44 status of LKCD into Linux Kernel Hiro Yoshioka
2002-02-14 5:56 ` Jeff Garzik
2002-02-14 6:33 ` Matt D. Robinson [this message]
2002-02-14 8:54 ` [lkcd-general] " Go Taniguchi
2002-02-15 2:42 ` Hiro Yoshioka
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=3C6B5A2E.2C2637C7@alacritech.com \
--to=yakker@alacritech.com \
--cc=hyoshiok@miraclelinux.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcd-general@lists.sourceforge.net \
/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