From: Martin Pluskal <martin@pluskal.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proper installation path for efi binaries (.efi)
Date: Mon, 04 Feb 2013 23:45:22 +0100 [thread overview]
Message-ID: <51103A02.5050108@pluskal.org> (raw)
In-Reply-To: <20130204223456.GA21225@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
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.
>
> Unless you really think that having /usr/ as a vfat filesystem is ok?
> :)
>
> thanks,
>
> greg k-h
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 898 bytes --]
next prev parent reply other threads:[~2013-02-04 22:45 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 [this message]
2013-02-04 22:59 ` Greg KH
2013-02-04 23:14 ` Martin Pluskal
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=51103A02.5050108@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