All of lore.kernel.org
 help / color / mirror / Atom feed
From: Louis Bouchard <louis.bouchard@canonical.com>
To: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: "kernel version not supported" message is causing concerns
Date: Tue, 30 Aug 2016 15:29:04 +0200	[thread overview]
Message-ID: <57C58A20.7000704@canonical.com> (raw)

Hello,

Every so often, I get questions or bug report about the fact that makedumpfile
issues the following message when running :

   The kernel version is not supported.
   The created dumpfile may be incomplete.

While I understand the requirement for this message, it almost systematically is
understood by users as "makedumpfile is broken".

I would like to discuss the opportunity of changing the wording of this message
so it appears less confusing. Maybe something like :

Warning: makedumpfile has not been tested on this version of the kernel.
         If the created dumpfile is incomplete, you may need to upgrade to a
         newer version of makedumpfile.

I would be happy to propose a pull request for such a change if accepted.

Kind regards,

...Louis


-- 
Louis Bouchard
Software engineer, Cloud & Sustaining eng.
Canonical Ltd
Ubuntu developer                       Debian Maintainer
GPG : 429D 7A3B DD05 B6F8 AF63  B9C4 8B3D 867C 823E 7A61

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

             reply	other threads:[~2016-08-30 13:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30 13:29 Louis Bouchard [this message]
2016-09-02  8:50 ` "kernel version not supported" message is causing concerns Atsushi Kumagai

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=57C58A20.7000704@canonical.com \
    --to=louis.bouchard@canonical.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 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.