From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: grub2 uefi x86_64 standalone image feature request
Date: Fri, 23 Dec 2011 17:02:53 +0100 [thread overview]
Message-ID: <4EF4A62D.90608@gmail.com> (raw)
In-Reply-To: <CAMPnHXxB=Nd=V1tCc7pHxkvrmyMnWkHV=tjis4mUAJoBjA7yDQ@mail.gmail.com>
On 23.12.2011 16:48, Keshav P R wrote:
> Hi,
> Is there any way to obtain the path info from which a standalone
> grub.efi was launched. In case of grub-mkimage uisng --prefix=""
> results in prefix being set to the dir from which the efi app was
> launched, but in the standalone grub.efi the prefix is
> (memdisk)/boot/grub . In (memdisk)/boot/grub/grub.cfg I added a search
> and configfile option that points to the external grub.cfg (in
> <UEFISYS>/efi/grub/grub.cfg), but I don't want to hardcode the
> grub.cfg file path in the configfile command in the memdisk grub.cfg.
>
> Is it possible to introduce a env var within grub2 (independent of
> prefix) which gives the path (grub style) from which the grub.efi file
> was launched by the firmware, so that I can do "configfile
> (path_from_which_grub.efi_loaded)/grub.cfg" in
> (memdisk)/boot/grub/grub.cfg in the standalone file. I want the
> standalone file to be be portable, no hardcoding of path of external
> grub.cfg file (which is editable by the user). Thanks in advance.
>
Patches are welcome.
> Regards.
>
> Keshav
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
prev parent reply other threads:[~2011-12-23 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 15:48 grub2 uefi x86_64 standalone image feature request Keshav P R
2011-12-23 16:02 ` Vladimir 'φ-coder/phcoder' Serbinenko [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=4EF4A62D.90608@gmail.com \
--to=phcoder@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 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.