From: Arjan van de Ven <arjan@infradead.org>
To: Takao Indoh <indou.takao@soft.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, lkdump-develop@lists.sourceforge.net
Subject: Re: [ANNOUNCE 0/7] Diskdump 1.0 Release
Date: Mon, 29 Nov 2004 12:19:52 +0100 [thread overview]
Message-ID: <1101727191.2814.52.camel@laptop.fenrus.org> (raw)
In-Reply-To: <3AC4D5FF1413D5indou.takao@soft.fujitsu.com>
On Mon, 2004-11-29 at 19:35 +0900, Takao Indoh wrote:
> Hi, all!
> I release diskdump 1.0 for kernel 2.6.9. It can be downloaded from
> the following site. Please feel free to use it!
> http://sourceforge.net/projects/lkdump
>
> Diskdump project is a joint development of RedHat and Fujitsu, and I'd
I think the company name is spelled Red Hat ;)
> like to express my gratitude to a RedHat developers for many comments
> and advices.
Can you explain to me why anyone would want to use this invasive patch
(it requires all drivers to change) instead of the kexec-dump approach? The
kexec-dump approach appears on first sight to be far cleaner and far more powerful,
so there must be a reason this work was done regardless of that.. I'm curious
what those reasons are, eg what's the advantage ???
next prev parent reply other threads:[~2004-11-29 11:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 10:35 Takao Indoh
2004-11-29 10:37 ` [ANNOUNCE 1/7] " Takao Indoh
2004-11-30 3:23 ` Rusty Russell
2004-12-01 0:50 ` Takao Indoh
2004-11-29 10:39 ` [ANNOUNCE 2/7] " Takao Indoh
2004-11-29 10:41 ` [ANNOUNCE 3/7] " Takao Indoh
2004-11-30 3:24 ` Rusty Russell
2004-11-29 10:43 ` [ANNOUNCE 4/7] " Takao Indoh
2004-11-29 10:45 ` [ANNOUNCE 5/7] " Takao Indoh
2004-11-29 10:47 ` [ANNOUNCE 6/7] " Takao Indoh
2004-11-29 10:48 ` [ANNOUNCE 7/7] " Takao Indoh
2004-11-29 11:19 ` Arjan van de Ven [this message]
2004-11-29 12:34 ` [lkdump-develop] Re: [ANNOUNCE 0/7] " Takao Indoh
2004-11-29 12:45 ` Arjan van de Ven
2004-11-30 1:15 ` Takao Indoh
2004-11-30 12:35 ` Arjan van de Ven
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=1101727191.2814.52.camel@laptop.fenrus.org \
--to=arjan@infradead.org \
--cc=indou.takao@soft.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkdump-develop@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
all inboxes | Powered by JetHome®