From: Thomas Renninger <trenn-l3A5Bk7waGM@public.gmane.org>
To: WANG Chao <chaowang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
Julian Wolf <juwolf-l3A5Bk7waGM@public.gmane.org>,
Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Baoquan He <bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: kdump in dracut
Date: Tue, 18 Feb 2014 11:58:38 +0100 [thread overview]
Message-ID: <1745934.e2BrRKeI5B@skinner> (raw)
In-Reply-To: <20140218034132.GG18964-2coKmSd1Zb6BYdNaKHuJJRcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
On Tuesday, February 18, 2014 11:41:32 AM WANG Chao wrote:
> CC Vivek, Bao
>
> On 02/17/14 at 04:10pm, Thomas Renninger wrote:
> > Hi,
> >
> > it looks like Redhat has made up their own kdump dracut module
> > in the kexec-tools Fedora package:
> > http://pkgs.fedoraproject.org/cgit/kexec-tools.git/tree/
> >
> > dracut-kdump.sh
> > dracut-module-setup.sh
> > dracut-monitor-dd-progress.sh
> >
> > I wonder whether there are any plans to get those into the
> > dracut mainline git repository.
>
> Hi, Thomas
>
> AFAICT, we don't have any plan to move these files into dracut.
> We want to maintain these files separately, because kdump initrd serves
> for a different purpose comparing to a normal initrd created by dracut
> by default. Basically we are reusing the dracut framework to achieve our
> own purpose (kdump).
"Own" purpose sounds strange. Kdump is something every distribution has
or should have.
I also do not understand the "kdump initrd serves for a different purpose"
argue.
Dracut is made to build an initrd for any purpose?
> > Otherwise we (SUSE) and others will have to come up with our
> > own implementations and we are where we do not want to end up:
> > Different initrd implementations, setups, configurations across
> > Linux distributions.
>
> This kdump module is highly associated with other scripts we provide in
> our kexec-tools package. What's the worse is that some parts are
> hardcoded for Fedora.
That's bad.
The stuff should (at least in dracut git repo) be compatible with:
ftp://kernel.org/pub/linux/utils/kernel/kexec
https://sourceforge.net/projects/makedumpfile
and other mainline projects.
We also had some specialities implemented in our mkinitrd solution.
But it should not be hard to put a basic dracut kdump module together
which is compatible.
> Thank you for bringing this up. It's really not my call. I'd like to
> hear from others in our team. And an ACK from Harald is also a must.
Sure.
Thanks,
Thomas
next prev parent reply other threads:[~2014-02-18 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 15:10 kdump in dracut Thomas Renninger
2014-02-18 3:41 ` WANG Chao
[not found] ` <20140218034132.GG18964-2coKmSd1Zb6BYdNaKHuJJRcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
2014-02-18 10:58 ` Thomas Renninger [this message]
2014-02-18 11:45 ` Vivek Goyal
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=1745934.e2BrRKeI5B@skinner \
--to=trenn-l3a5bk7wagm@public.gmane.org \
--cc=bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=chaowang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=juwolf-l3A5Bk7waGM@public.gmane.org \
--cc=vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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 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.