public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Maxim Kammerer <mk@dee.su>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proper installation path for efi binaries (.efi)
Date: Sat, 9 Feb 2013 05:21:13 +0200	[thread overview]
Message-ID: <CAHsXYDDiZyFVcENR_WeK6p8vtUASESky-6P166hmhC3bkU+Gzg@mail.gmail.com> (raw)
In-Reply-To: <511040E1.207@pluskal.org>

On Tue, Feb 5, 2013 at 1:14 AM, Martin Pluskal <martin@pluskal.org> wrote:
> 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 ...)).

I think that you will most certainly need to separate installation and
configuration (e.g., with a "shim-install" script or similar), because
configuration depends on the environment. For instance, with removable
media you will need to:
1. Drop shim.efi and MokManager.efi into [/boot/]EFI/BOOT.
2. Rename BOOTx64.EFI to grubx64.efi, and then rename shim.efi to BOOTx64.EFI.
(Copied from http://dee.su/liberte-install — this has been tested with
OVMF and real Secure Boot hardware.)

-- 
Maxim Kammerer
Liberté Linux: http://dee.su/liberte


      parent reply	other threads:[~2013-02-09  3:21 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
2013-02-05  4:24         ` Alec Warner
2013-02-05 10:05           ` Chí-Thanh Christopher Nguyễn
2013-02-09  3:21         ` Maxim Kammerer [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=CAHsXYDDiZyFVcENR_WeK6p8vtUASESky-6P166hmhC3bkU+Gzg@mail.gmail.com \
    --to=mk@dee.su \
    --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