From: Xunlei Pang <xpang@redhat.com>
To: Philip Prindeville <philipp_subx@redfish-solutions.com>,
Bhupesh Sharma <bhsharma@redhat.com>
Cc: horms@verge.net.au, kexec@lists.infradead.org, ebiederm@xmission.com
Subject: Re: No man page for kdump (yet?)
Date: Thu, 13 Apr 2017 09:52:17 +0800 [thread overview]
Message-ID: <58EED9D1.10007@redhat.com> (raw)
In-Reply-To: <4078F15B-E15A-40A8-B7A7-FB5BFBC4CFCB@redfish-solutions.com>
On 04/11/2017 at 05:26 AM, Philip Prindeville wrote:
>> On Apr 10, 2017, at 5:57 AM, Bhupesh Sharma <bhsharma@redhat.com> wrote:
>>
>> Hi,
>>
>> It seems the latest upstream kexec-tools does support a complete man
>> page for kdump yet:
>>
>> DESCRIPTION
>> kdump does not have a man page yet.
>>
>> I would propose having a propose having a man page for kdump (as the
>> feature is quite useful and has matured over time).
>>
>> I can work to cook up a patch for the same.
>>
>> Please let me know if this makes sense or if there are any objections
>> to the same.
>>
>> Regards,
>> Bhupesh
>
> Personally I’d welcome one.
This tool(/usr/sbin/kdump) looks like "cp /proc/vmcore" under kdump,
does anyone know its existent/potential users?
Regards,
Xunlei
>
> -Philip
>
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2017-04-13 1:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 11:57 No man page for kdump (yet?) Bhupesh Sharma
2017-04-10 21:26 ` Philip Prindeville
2017-04-13 1:52 ` Xunlei Pang [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=58EED9D1.10007@redhat.com \
--to=xpang@redhat.com \
--cc=bhsharma@redhat.com \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=philipp_subx@redfish-solutions.com \
--cc=xlpang@redhat.com \
/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