From: Gnanasekar Loganathan <l.gnanasekar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: increasing grubenv file size
Date: Thu, 2 Dec 2010 13:05:01 +0530 [thread overview]
Message-ID: <AANLkTimBs=6GOpk5D93PQc8hP2uC+E7mdf+CEK_yy-fU@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikBFhqfEF=VvzxYAVy01CYe3mwKYkD4eEOzr5O5@mail.gmail.com>
Hi Jordan,
Hope so all these environment variables being set from the grub itself
using "set".
Anyhow saving in separate file option is sounds good.
Thanks Jordan.
Thanks,
Gnana
On Thu, Dec 2, 2010 at 11:56 AM, Jordan Uggla <jordan.uggla@gmail.com> wrote:
> On Wed, Dec 1, 2010 at 8:57 PM, Gnanasekar Loganathan
> <l.gnanasekar@gmail.com> wrote:
>> Hi Colin,
>>
>> We are storing environment variables like below:
>>
>> macaddr=ab:cd:ef:12:34:56
>> bootfile=image.gnana
>> ipaddr=172.30.16.203
>> netmask=255.255.0.0
>> serverip=172.30.16.90
>> gatewayip=172.16.1.1
>> ftpuser=username
>> ftppasswd=password
>> bootcmd=flash(0,0):XXXX-OS-8-3-9-23.bin;default_boot;boot
>
> Are these environment variables being *set* from within grub itself,
> or by an administrator booted into an OS? For persistent storage of
> environment variables you can simply set the variables with the
> grub.cfg, or in a separate cfg file which is sourced by the primary
> grub.cfg (like /boot/grub/custom.cfg). Using a normal text file you
> can include as many variables as you want, expanding as needed.
>
> That's not to say that it will never be useful to have a larger
> grubenv, but it doesn't sound like it's needed in your case.
>
> --
> Jordan Uggla (Jordan_U on irc.freenode.net)
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
prev parent reply other threads:[~2010-12-02 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 5:15 increasing grubenv file size Gnanasekar Loganathan
2010-12-01 10:24 ` Colin Watson
2010-12-02 4:57 ` Gnanasekar Loganathan
2010-12-02 6:26 ` Jordan Uggla
2010-12-02 7:35 ` Gnanasekar Loganathan [this message]
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='AANLkTimBs=6GOpk5D93PQc8hP2uC+E7mdf+CEK_yy-fU@mail.gmail.com' \
--to=l.gnanasekar@gmail.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 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).