All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Michael Brown <mcb30@ipxe.org>
Cc: ipxe-devel <ipxe-devel@ipxe.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [ipxe-devel] EFI_PXE_BASE_CODE_PROTOCOL
Date: Thu, 10 Sep 2015 17:20:26 +0200	[thread overview]
Message-ID: <1441898426.11233.37.camel@redhat.com> (raw)
In-Reply-To: <55F19C96.50709@ipxe.org>

  Hi,

> > The file is simply placed as "grub.cfg" in tftproot, next to grubx64.efi
> 
> Thanks.  From my experiments, it seems that GRUB is using the hardcoded 
> path /efi/boot/grub.cfg to locate the configuration file, regardless of 
> where grub.efi was loaded from.

Hmm, probably depends on how you are building it.  There are also tools
like grub2-mknetdir and grub2-mkstandalone.  Pretty confusing :(

I'm using the binary shipped with RHEL.  The centos one should show the
same behavior.

https://ftp.fau.de/centos/7.1.1503/os/x86_64/EFI/BOOT/

There is a pretty readable grub.cfg file too btw.

Given there are no grub2 modules anywhere I suspect that binary was
created with grub2-mkstandalone.

HTH,
  Gerd

  reply	other threads:[~2015-09-10 15:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-07 10:14 [Qemu-devel] EFI_PXE_BASE_CODE_PROTOCOL Gerd Hoffmann
2015-09-07 14:02 ` [Qemu-devel] [ipxe-devel] EFI_PXE_BASE_CODE_PROTOCOL Michael Brown
2015-09-07 14:58   ` Gerd Hoffmann
2015-09-10 15:07     ` Michael Brown
2015-09-10 15:20       ` Gerd Hoffmann [this message]
2015-09-10 15:29         ` Michael Brown
2015-09-11  8:56           ` Gerd Hoffmann
2015-10-20  8:16             ` Gerd Hoffmann
2015-10-26  0:14               ` Michael Brown

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=1441898426.11233.37.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=ipxe-devel@ipxe.org \
    --cc=mcb30@ipxe.org \
    --cc=qemu-devel@nongnu.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.