Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jay Lan <jlan@sgi.com>
To: kexec@lists.infradead.org
Subject: Kdump Automation Mechanism
Date: Wed, 20 Aug 2008 13:07:53 -0700	[thread overview]
Message-ID: <48AC7999.2020104@sgi.com> (raw)
In-Reply-To: <536253.14632.qm@web1114.biz.mail.sk1.yahoo.com>

Cai Qian wrote:
> Hi Bernhard and Neil,
> 
> --- Bernhard Walle <bwalle@suse.de> wrote:
> 
>> * Jay Lan [2008-08-14 10:23]:
>>> If you can put vmcore at the same location... Ahh, asking too much? ;)
>> Will change that to /var/crash since that's FHS 2.3 anyway. :)
>> [And I personally never liked ???/var/log/dump??? since it's not a logfile.]
>>
> 
> That's a good. Do you have any consideration for standard Kdump options? I have created a Kdump
> test suite but it originally written and tested on RHEL and Fedora.
> 
> http://sourceforge.net/mailarchive/message.php?msg_name=20080815.210735.450985660335275199.qcai%40redhat.com

Hi Cai,

I clicked on the attachment of the page above, it failed with:
   File not found on server.

Regards,
 - jay

> 
> I hope it could also work for SLES, OpenSUSE and other distros. However, I have no environment to
> test it yet, and I found it is kind of difficult to port it to other distros for so many different
> options.
> 
> I'd appreciate if you guys could have a look, and come out a standard Kdump options. I'd also be
> happy to modify the suite accordingly.
> 
> Thanks,
> CaiQian
> 
>>
>> Bernhard
>> -- 
>> Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
>>
>> ???Make everything as simple as possible, but not simpler.???
>>        -- Albert Einstein
>>
>> _______________________________________________
>> kexec mailing list
>> kexec at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/kexec
>>
> 
> 
> _______________________________________________
> kexec mailing list
> kexec at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
> 



  parent reply	other threads:[~2008-08-20 20:07 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 [this message]
2008-08-21  3:03                 ` Cai Qian
2008-08-14 13:34 ` 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=48AC7999.2020104@sgi.com \
    --to=jlan@sgi.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox