From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH, RFC, RFT] Mactel integration
Date: Tue, 29 Nov 2011 10:00:38 +0100 [thread overview]
Message-ID: <4ED49F36.50905@gmail.com> (raw)
In-Reply-To: <CAMPnHXygSyM=JuOgreKX-B33LM49S+KirM018h83mYeotJUNkw@mail.gmail.com>
On 29.11.2011 08:25, Keshav P R wrote:
> grubx64.efi is installed at /boot/efi/efi/grub2/grubx64.efi , but the
> modules are located at /boot/grub (which is $grubdir aka prefix set in
> grubx64.efi/core.efi). But this again creates confusion for some users
> who have to find out the "actual" prefix dir in case he/she wants to
> modify grub.cfg and grubenv in that dir. The only way to force
> grub-install to install "everything" in /boot/efi/efi/grub/ is to us
The modules and configuration files form platform-independent part as
far as install is concerned (it's always handles the same way). The
grub.efi is the EFI specific part which needs to go where EFI expects
it. /efi directory on ESP as its name implies stores files for EFI,
perhaps some small config files, it is not to store our bunch of
modules. It's ok to use ESP to store modules unless they go into /efi
directory but it's hard to say if such a long list of files will trigger
any bugs in firmware implementation but in any case platform-independent
part shouldn't go into firmware-specific directories. We've already had
issues with IEEE1275 when we did something similar
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
next prev parent reply other threads:[~2011-11-29 9:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 13:25 [PATCH, RFC, RFT] Mactel integration Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-28 14:27 ` Mads Kiilerich
2011-11-28 14:50 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-28 22:23 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-28 22:29 ` Seth Goldberg
2011-11-29 6:34 ` Seth Goldberg
2011-11-29 7:25 ` Keshav P R
2011-11-29 8:05 ` Seth Goldberg
2011-11-29 9:00 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-12-02 6:22 ` Keshav P R
2011-12-02 6:53 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4ED49F36.50905@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 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).