From: Andrey Borzenkov <arvidjaar@gmail.com>
To: Rigoberto Corujo <rcorujo@yahoo.com>
Cc: "help-grub@gnu.org" <help-grub@gnu.org>,
"grub-devel@gnu.org" <grub-devel@gnu.org>
Subject: Re: Obtaining the MAC address of the boot NIC for a PXE boot
Date: Sat, 11 May 2013 08:47:02 +0400 [thread overview]
Message-ID: <20130511084702.3b23ee24@opensuse.site> (raw)
In-Reply-To: <1368202377.58319.YahooMailNeo@web120202.mail.ne1.yahoo.com>
В Fri, 10 May 2013 09:12:57 -0700 (PDT)
Rigoberto Corujo <rcorujo@yahoo.com> пишет:
>
> Thank you Andrey. I can confirm that the net_default_interface, net_default_ip, and net_default_mac variables worked as expected. I did notice, however, then when I'm in the grub shell and I type "set", these variables show up in the list, but they have no values, which makes it appear as if something is wrong. If I echo the variables, however, I do see their correct values.
>
Does it behave better with patch below?
diff --git a/grub-core/kern/corecmd.c b/grub-core/kern/corecmd.c
index cfab676..1700eb4 100644
--- a/grub-core/kern/corecmd.c
+++ b/grub-core/kern/corecmd.c
@@ -40,7 +40,7 @@ grub_core_cmd_set (struct grub_command *cmd __attribute__ ((unused)),
{
struct grub_env_var *env;
FOR_SORTED_ENV (env)
- grub_printf ("%s=%s\n", env->name, env->value);
+ grub_printf ("%s=%s\n", env->name, grub_env_get (env->name));
return 0;
}
next prev parent reply other threads:[~2013-05-11 4:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1367240132.58582.YahooMailNeo@web120204.mail.ne1.yahoo.com>
2013-05-01 14:59 ` Obtaining the MAC address of the boot NIC for a PXE boot Andrey Borzenkov
2013-05-04 21:08 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-05-04 21:19 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-05-05 5:17 ` Andrey Borzenkov
2013-05-07 10:03 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-05-07 17:50 ` Documentation for (Re: Obtaining the MAC address of the boot NIC for a PXE boot) Andrey Borzenkov
2013-05-07 19:45 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-05-08 14:52 ` Andrey Borzenkov
2013-05-11 16:35 ` New command eval Andrey Borzenkov
2013-05-11 17:02 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-05-11 17:30 ` Andrey Borzenkov
2013-05-14 6:26 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-05-12 0:07 ` Seth Goldberg
2013-05-12 5:39 ` Andrey Borzenkov
2013-05-13 5:13 ` Seth Goldberg
2013-05-14 7:21 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-05-08 17:27 ` Obtaining the MAC address of the boot NIC for a PXE boot Rigoberto Corujo
2013-05-08 19:25 ` Andrey Borzenkov
2013-05-10 16:12 ` Rigoberto Corujo
2013-05-11 4:47 ` Andrey Borzenkov [this message]
2013-05-15 17:09 ` Rigoberto Corujo
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=20130511084702.3b23ee24@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=help-grub@gnu.org \
--cc=rcorujo@yahoo.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).