From: Jeff Garzik <jgarzik@pobox.com>
To: linux-kernel@vger.kernel.org
Cc: Takao Indoh <indou.takao@soft.fujitsu.com>,
lkcd-devel@lists.sourceforge.net
Subject: Re: [RFC] Standard filesystem types for crash dumping
Date: Wed, 14 Jul 2004 03:49:35 -0400 [thread overview]
Message-ID: <40F4E58F.7040204@pobox.com> (raw)
In-Reply-To: <11077.1089790663@kao2.melbourne.sgi.com>
Keith Owens wrote:
> Follow ups to lkml please, to keep any discussion on the same list.
>
> Several kernel additions exist for saving crash dump information, among
> them are lkcd, crash, kmsgdump. They all have the same problems :-
>
> * Where to store the crash data.
> * How to write data when the kernel is unreliable, it may not be
> servicing interrupts.
> * User space needs to read and clear the dump data.
> * Performance!
> * Coexistence of multiple dump drivers.
Have you tried diskdump?
It already exists, and seems to address these things.
Jeff
next prev parent reply other threads:[~2004-07-14 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 7:37 [RFC] Standard filesystem types for crash dumping Keith Owens
2004-07-14 7:49 ` Jeff Garzik [this message]
2004-07-14 10:55 ` Keith Owens
2004-07-16 16:43 ` Pavel Machek
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=40F4E58F.7040204@pobox.com \
--to=jgarzik@pobox.com \
--cc=indou.takao@soft.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcd-devel@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 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.