From: Pingfan Liu <piliu@redhat.com>
To: kexec@lists.infradead.org
Subject: [PATCH] doc: vmcore-dmesg should work on ELF format
Date: Wed, 27 Nov 2019 11:12:33 +0800 [thread overview]
Message-ID: <1574824353-5309-1-git-send-email-piliu@redhat.com> (raw)
User may mistake to run vmcore-dmesg against an kdump format dumpfile, and
fail to get kernel message.
Signed-off-by: Pingfan Liu <piliu@redhat.com>
---
vmcore-dmesg/vmcore-dmesg.8 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/vmcore-dmesg/vmcore-dmesg.8 b/vmcore-dmesg/vmcore-dmesg.8
index d9e3c62..dc06909 100644
--- a/vmcore-dmesg/vmcore-dmesg.8
+++ b/vmcore-dmesg/vmcore-dmesg.8
@@ -27,7 +27,7 @@ vmcore-dmesg \- This is just a placeholder until real man page has been written
.\" respectively.
\fBvmcore-dmesg\fP extracts the dmesg from a vmcore and write it to
standard out. \fBvmcore-dmesg\fP works against either
-\fB/proc/vmcore\fP in a crash dump capture context or a copy
+\fB/proc/vmcore\fP in a crash dump capture context or a ELF format copy
of \fB/proc/vmcore\fP that has been saved for later analysis. A
single build of \fBvmcore-dmesg\fP should work against any linux
vmcore written created on any architecture.
--
2.7.5
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
reply other threads:[~2019-11-27 3:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1574824353-5309-1-git-send-email-piliu@redhat.com \
--to=piliu@redhat.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