From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: support for crashkernel= in 10_linux.in
Date: Wed, 24 Jun 2009 14:11:59 +0200 [thread overview]
Message-ID: <20090624121159.GC1429@thorin> (raw)
In-Reply-To: <20090624112049.GU11691@tas>
Hi Michael,
On Wed, Jun 24, 2009 at 01:20:49PM +0200, Michael Vogt wrote:
> diff -Nur -x '*.orig' -x '*~' grub2-1.96+20090611/util/grub.d/10_linux.in grub2-1.96+20090611.new/util/grub.d/10_linux.in
> --- grub2-1.96+20090611/util/grub.d/10_linux.in 2009-06-24 10:17:45.202761012 +0200
> +++ grub2-1.96+20090611.new/util/grub.d/10_linux.in 2009-06-24 10:19:11.198757708 +0200
> @@ -43,6 +43,11 @@
> LINUX_ROOT_DEVICE=UUID=${GRUB_DEVICE_UUID}
> fi
>
> +# add crashkernel option if we have the requierd tools
> +if [ -x "/usr/bin/makedumpfile" ] && [ -x "/sbin/kexec" ]; then
> + GRUB_CMDLINE_EXTRA="$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M"
> +fi
> +
So many variables start to look confusing. Can't you append it to one of
the others?
Or give it a more explicit name, like ${GRUB_CMDLINE_LINUX_CRASHADDR} or so
(in any case GRUB_CMDLINE_EXTRA is too generic for a Linux-specific thing).
> linux_entry "${OS}, Linux ${version}" \
> - "${GRUB_CMDLINE_LINUX} ${GRUB_CMDLINE_LINUX_DEFAULT}"
> + "${GRUB_CMDLINE_LINUX} ${GRUB_CMDLINE_LINUX_DEFAULT} ${GRUB_CMDLINE_EXTRA}"
> linux_entry "${OS}, Linux ${version} (recovery mode)" \
> "single ${GRUB_CMDLINE_LINUX}"
Is this flag not desireable in recovery mode?
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-06-24 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 11:20 support for crashkernel= in 10_linux.in Michael Vogt
2009-06-24 12:11 ` Robert Millan [this message]
2009-06-24 13:11 ` Michael Vogt
2009-06-24 19:18 ` Pavel Roskin
2009-06-24 20:55 ` Robert Millan
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=20090624121159.GC1429@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.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.