All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Cai Qian <caiqian@cclom.cn>
Cc: kexec@lists.infradead.org
Subject: Re: Kdump Automation Mechanism
Date: Thu, 14 Aug 2008 09:34:03 -0400	[thread overview]
Message-ID: <20080814133403.GA4157@redhat.com> (raw)
In-Reply-To: <249026.52731.qm@web1110.biz.mail.sk1.yahoo.com>

On Thu, Aug 14, 2008 at 01:03:48AM -0700, Cai Qian wrote:
> Hi,
> 
> I am wondering if this is the right project to accept Kdump automation files. For example, Kdump
> daemon init script, mkdumprd (read from Kdump configuration file and generate Kdump initramfs for
> the system), default Kdump configuration file, tools to compress vmcore etc.
> 
> The problem I am having right now is that, I am trying to write a Kdump test suite, but I could
> not 
> find a easy way to write a general enough suite for every distro to use. Red Hat and SUSE have
> slightly different setting up. Debian and Ubuntu don't have Kdump automation mechanism as the time
> I was checking. Also, It make things much easier for different distros and users to pick it up and
> contribute to those efforts.
> 

Couln't agree more. Distributions tend to diverge when it comes to user
space implementation of things and that makes testing and community
contribution very difficult (Apart from normal user being confused).

We need to put some effort in making sure we diverge as less as possible.
How to do that? I can think of two things.

- Development of user space utilities/applications takes place while
  interacting with community. For example, filtering utility, makedumpfile
  development took place while taking feedback from community on kexec
  mailing list.

- Willingness on the user space developers to come to a common platform
  and put a concious effort to keep things similar.  (Of course good
  things similar).

Thanks
Vivek

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

      parent reply	other threads:[~2008-08-14 13:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-14  8:03 Kdump Automation Mechanism Cai Qian
2008-08-14  8:17 ` Bernhard Walle
2008-08-14 12:18   ` Neil Horman
2008-07-18  0:43     ` Bernhard Walle
2008-08-14 15:11       ` Neil Horman
2008-08-14 17:23         ` Jay Lan
2008-08-14 18:52           ` Neil Horman
2008-08-18 15:02           ` Bernhard Walle
2008-08-20 16:22             ` Cai Qian
2008-08-20 19:54               ` Bernhard Walle
2008-08-20 20:07               ` Jay Lan
2008-08-21  3:03                 ` Cai Qian
2008-08-14 13:34 ` Vivek Goyal [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=20080814133403.GA4157@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=caiqian@cclom.cn \
    --cc=kexec@lists.infradead.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.