From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Save/Load environment variable support
Date: Sat, 14 Jun 2008 20:47:57 +0200 [thread overview]
Message-ID: <20080614184757.GH5636@thorin> (raw)
In-Reply-To: <ca0f59980806130007u25b35b31l70028fe2c488ca8e@mail.gmail.com>
On Fri, Jun 13, 2008 at 03:07:54PM +0800, Bean wrote:
> Hi,
>
> I separate the save/load environment variable function from my
> previous patch on environment block. It contains the command
> save_env/load_env/list_env and tool grub-editenv, but without the
> kernel patch.
> --
> Bean
>
> diff --git a/commands/loadenv.c b/commands/loadenv.c
> new file mode 100755
> index 0000000..970baf3
> --- /dev/null
> +++ b/commands/loadenv.c
> @@ -0,0 +1,250 @@
> +/* loadenv.c - command to load/save environment variable. */
Is this useful as a standalone command? If we're in a stage in which commands
can be executed, the same effect could be archieved with the "." command on
a grub.cfg-like formatted file?
IIRC you explained that this feature could be useful as the basis for
findroot style search, or to override existing variables like "root", "prefix"
or "default". In both cases (if I understood correctly) you want it to be run
automaticaly as the init routine for your module.
However if your code is small enough, maybe it could replace the existing
use of grub_prefix (I commented this on the other mail), thereby reducing
kernel size and making it preferable to be part of kernel than a separate
module. Do you think that's possible?
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What good is a phone call… if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-06-14 18:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 7:07 [PATCH] Save/Load environment variable support Bean
2008-06-14 18:47 ` Robert Millan [this message]
2008-06-14 19:03 ` Bean
2008-06-14 19:20 ` Robert Millan
2008-06-14 19:28 ` Bean
2008-06-14 19:30 ` Robert Millan
2008-06-14 19:44 ` Bean
2008-06-15 13:25 ` Robert Millan
2008-06-15 14:09 ` Bean
2008-06-30 13:06 ` Bean
2008-07-01 15:54 ` Robert Millan
2008-07-02 7:39 ` Bean
2008-07-03 18:04 ` Marco Gerards
2008-07-03 18:09 ` Pavel Roskin
2008-07-03 20:11 ` Bean
2008-07-03 22:52 ` Robert Millan
2008-07-03 20:41 ` Marco Gerards
2008-07-03 21:06 ` Bean
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=20080614184757.GH5636@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.