From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] savedefault
Date: Thu, 11 Jun 2009 22:05:50 +0200 [thread overview]
Message-ID: <20090611200550.GA28915@thorin> (raw)
In-Reply-To: <d7ead6de0906010348n404e046o207766ba3554ac1f@mail.gmail.com>
Hi!
On Mon, Jun 01, 2009 at 12:48:38PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> cat << EOF
> +load_env
> set default=${GRUB_DEFAULT}
Does the "set" line override the settings in load_env? It looks like it
would.
> --- a/util/grub.d/10_freebsd.in
> +++ b/util/grub.d/10_freebsd.in
> @@ -57,6 +57,8 @@ if [ "x$kfreebsd" != "x" ] ; then
>
> cat << EOF
> menuentry "${OS}" {
> + saved_entry=\${chosen_entry}
> + save_env saved_entry
> EOF
> prepare_grub_to_access_device ${GRUB_DEVICE_BOOT} | sed -e "s/^/\t/"
> cat << EOF
> diff --git a/util/grub.d/10_hurd.in b/util/grub.d/10_hurd.in
> index 12d61b0..114017b 100644
> --- a/util/grub.d/10_hurd.in
> +++ b/util/grub.d/10_hurd.in
> @@ -70,6 +70,8 @@ fi
>
> cat << EOF
> menuentry "${OS}" {
> + saved_entry=\${chosen_entry}
> + save_env saved_entry
> EOF
> prepare_grub_to_access_device ${GRUB_DEVICE} | sed -e "s/^/\t/"
> cat << EOF
> diff --git a/util/grub.d/10_linux.in b/util/grub.d/10_linux.in
> index c2da413..93d141b 100644
> --- a/util/grub.d/10_linux.in
> +++ b/util/grub.d/10_linux.in
> @@ -97,6 +97,8 @@ linux_entry ()
> {
> cat << EOF
> menuentry "$1" {
> + saved_entry=\${chosen_entry}
> + save_env saved_entry
> EOF
> prepare_grub_to_access_device ${GRUB_DEVICE_BOOT} | sed -e "s/^/\t/"
> cat << EOF
I think it'd really be a good idea to either factorize this into a function
(ala prepare_grub_to_access_device), or make it part of the scripting engine.
I'm afraid of the possibility that later we want to change something and can't
because 3rd party scripts depend on it (this happened with disk selection
before we had prepare_grub_to_access_device).
--
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-11 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 10:48 [PATCH] savedefault Vladimir 'phcoder' Serbinenko
2009-06-07 7:50 ` Felix Zielcke
2009-06-07 9:14 ` Vladimir 'phcoder' Serbinenko
2009-06-07 9:35 ` Bean
2009-06-07 14:51 ` Vladimir 'phcoder' Serbinenko
2009-06-08 7:37 ` Bean
2009-06-11 18:38 ` Vladimir 'phcoder' Serbinenko
2009-06-11 20:05 ` Robert Millan [this message]
2009-06-12 1:04 ` Pavel Roskin
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=20090611200550.GA28915@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.