All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: passing options to grub in xen,openfirmware and efi
Date: Thu, 23 Apr 2015 11:43:30 +0200	[thread overview]
Message-ID: <20150423094330.GA7326@aepfle.de> (raw)
In-Reply-To: <CAA91j0XL3zt9PkyquuQ89oB-R1Hs+d=gKd3RQg6SC_iLQ-GBrQ@mail.gmail.com>

On Thu, Apr 23, Andrei Borzenkov wrote:

> What I do not like is the possibility to blindly set any internal
> variable (consider overriding of $prefix). I'd prefer to set variables
> in separate namespace, like grub.arg.XXX=YYY for XXX=YYY argument and
> let user figure out what to do with them.

You mean if booted with 'boot hd:,grub foo=bar' a 'grub.arg.foo=bar'
should be available? That sounds like a plan.

Olaf


  reply	other threads:[~2015-04-23  9:43 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23  8:03 passing options to grub in xen,openfirmware and efi Olaf Hering
2015-04-23  9:35 ` Andrei Borzenkov
2015-04-23  9:43   ` Olaf Hering [this message]
2015-04-23  9:54     ` Andrei Borzenkov
2015-04-23 11:25       ` Olaf Hering
2015-04-23 11:40         ` Andrei Borzenkov
2015-04-23 12:17           ` Olaf Hering
2015-04-29 15:02   ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-04-29 15:10     ` Olaf Hering
2015-04-29 15:21       ` Vladimir 'phcoder' Serbinenko
2015-04-29 15:35         ` Olaf Hering
2015-04-29 15:41           ` Vladimir 'phcoder' Serbinenko
2015-04-29 15:48             ` Olaf Hering
2015-04-29 16:22               ` Vladimir 'phcoder' Serbinenko
2015-04-29 16:28                 ` Olaf Hering
2015-04-29 16:37                   ` Vladimir 'phcoder' Serbinenko
2015-04-29 16:49                     ` Olaf Hering
2015-05-07 14:45                       ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-05-07 14:54                         ` Olaf Hering
2015-05-07 14:59                           ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-05-07 15:03                             ` Andrei Borzenkov
2015-05-07 15:21                               ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-05-08 10:09                                 ` Olaf Hering
2015-05-08 10:57                                   ` Vladimir 'phcoder' Serbinenko
2015-05-08 11:06                                     ` Andrei Borzenkov
2015-05-08 11:17                                       ` Olaf Hering
2015-05-08 11:15                                     ` Olaf Hering
2015-05-08 11:33                                       ` Andrei Borzenkov
2015-05-08 11:46                                         ` Olaf Hering
2015-05-08 12:57                                           ` Vladimir 'phcoder' Serbinenko
2015-05-11  9:36                                         ` Olaf Hering
2015-05-11 10:22                                           ` Andrei Borzenkov
2015-05-11 10:43                                             ` Olaf Hering
2015-05-11 10:46                                               ` Vladimir 'phcoder' Serbinenko
2015-05-11 11:04                                                 ` Olaf Hering
2015-05-11 11:22                                                   ` Vladimir 'phcoder' Serbinenko
2015-05-11 14:10                                 ` Olaf Hering
2015-05-08 10:44                               ` Michael Chang
2015-04-23 17:05 ` Curt Brune

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=20150423094330.GA7326@aepfle.de \
    --to=olaf@aepfle.de \
    --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.