From: Martin Pluskal <martin@pluskal.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proper installation path for efi binaries (.efi)
Date: Tue, 05 Feb 2013 00:14:41 +0100 [thread overview]
Message-ID: <511040E1.207@pluskal.org> (raw)
In-Reply-To: <20130204225907.GA1696@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 2502 bytes --]
On 4.2.2013 23:59, Greg KH wrote:
> On Mon, Feb 04, 2013 at 11:45:22PM +0100, Martin Pluskal wrote:
>> On 4.2.2013 23:34, Greg KH wrote:
>>> On Mon, Feb 04, 2013 at 08:13:58PM +0100, Martin Pluskal wrote:
>>>> Hi
>>>> I am curious what is the proper path for installation of efi binaries
>>>> (such as shim.efi) in gentoo. I don't think that installing them
>>>> directly into /boot/efi... is proper way - it seems to me that
>>>> /usr/lib64/efi or /usr/libexec/efi is more appropriate location for
>>>> them. What's your opinion?
>>>
>>> It depends on if you want the bootloader to use the binary or not. If
>>> you do, it needs to be in /boot/efi/, otherwise it will never be able to
>>> be run by the UEFI system.
>> Well, in order to boot you have to place .efi into /boot/efi, I am not
>> sure if it is the best idea to directly install everything with .efi
>> into /boot/efi. As far as I know, elilo is installed into /usr/lib/elilo
>> and grub2 is placed into /boot/efi by grub2-install.
>
> If elilo is in /usr/lib/elilo, the UEFI bios can not run the binary as
> it can't even see the filesystem to read the binary from.
Well it cannot, elilo.efi has to be placed to /boot/efi, install path is
however /usr/lib/elilo/elilo.efi.
>
> So how can anything that is .efi _not_ be in /boot/efi and still work?
I am talking about location to which .efi is supposed to be placed after
installation, not necessary from which it can work.
>
> Have you tried this out on your system with any success?
Why would I try it? I am not suggesting that it would work. After you
emerge elilo or grub2 you are still not able to boot unless you do other
steps (grub2-install or cp elilo.efi /boot/efi... && efibootmgr ... etc.)
>
> What exactly is the issue you are trying to solve here?
I am thinking about creating ebuild for shim. I was wondering if there
is any policy or suggestion where to place .efi binaries or how to
handle them in gentoo - it seems that there is none so perhaps there
should be agreed on what best practice is (install directly into
/boot/efi or install else and let user manually copy .efi to /boot/efi
or something completely different (eselect efi ...)).
In suse default path is for example /usr/lib64/efi/:
ls /usr/lib64/efi/:
MokManager.efi elilo.efi shim-suse.efi shim.efi
xen-4.2.1_02-0.7.2.efi xen-4.2.efi xen-4.efi xen.efi
yet /boot/efi contains only elilo.efi
>
> thanks,
>
> greg k-h
>
thanks
Martin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 898 bytes --]
next prev parent reply other threads:[~2013-02-04 23:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 19:13 [gentoo-dev] Proper installation path for efi binaries (.efi) Martin Pluskal
2013-02-04 22:34 ` Greg KH
2013-02-04 22:45 ` Martin Pluskal
2013-02-04 22:59 ` Greg KH
2013-02-04 23:14 ` Martin Pluskal [this message]
2013-02-05 4:24 ` Alec Warner
2013-02-05 10:05 ` Chí-Thanh Christopher Nguyễn
2013-02-09 3:21 ` Maxim Kammerer
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=511040E1.207@pluskal.org \
--to=martin@pluskal.org \
--cc=gentoo-dev@lists.gentoo.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