1 |
On Mon, Feb 4, 2013 at 3:14 PM, Martin Pluskal <martin@×××××××.org> wrote: |
2 |
> On 4.2.2013 23:59, Greg KH wrote: |
3 |
>> On Mon, Feb 04, 2013 at 11:45:22PM +0100, Martin Pluskal wrote: |
4 |
>>> On 4.2.2013 23:34, Greg KH wrote: |
5 |
>>>> On Mon, Feb 04, 2013 at 08:13:58PM +0100, Martin Pluskal wrote: |
6 |
>>>>> Hi |
7 |
>>>>> I am curious what is the proper path for installation of efi binaries |
8 |
>>>>> (such as shim.efi) in gentoo. I don't think that installing them |
9 |
>>>>> directly into /boot/efi... is proper way - it seems to me that |
10 |
>>>>> /usr/lib64/efi or /usr/libexec/efi is more appropriate location for |
11 |
>>>>> them. What's your opinion? |
12 |
>>>> |
13 |
>>>> It depends on if you want the bootloader to use the binary or not. If |
14 |
>>>> you do, it needs to be in /boot/efi/, otherwise it will never be able to |
15 |
>>>> be run by the UEFI system. |
16 |
>>> Well, in order to boot you have to place .efi into /boot/efi, I am not |
17 |
>>> sure if it is the best idea to directly install everything with .efi |
18 |
>>> into /boot/efi. As far as I know, elilo is installed into /usr/lib/elilo |
19 |
>>> and grub2 is placed into /boot/efi by grub2-install. |
20 |
>> |
21 |
>> If elilo is in /usr/lib/elilo, the UEFI bios can not run the binary as |
22 |
>> it can't even see the filesystem to read the binary from. |
23 |
> Well it cannot, elilo.efi has to be placed to /boot/efi, install path is |
24 |
> however /usr/lib/elilo/elilo.efi. |
25 |
>> |
26 |
>> So how can anything that is .efi _not_ be in /boot/efi and still work? |
27 |
> I am talking about location to which .efi is supposed to be placed after |
28 |
> installation, not necessary from which it can work. |
29 |
>> |
30 |
>> Have you tried this out on your system with any success? |
31 |
> Why would I try it? I am not suggesting that it would work. After you |
32 |
> emerge elilo or grub2 you are still not able to boot unless you do other |
33 |
> steps (grub2-install or cp elilo.efi /boot/efi... && efibootmgr ... etc.) |
34 |
>> |
35 |
>> What exactly is the issue you are trying to solve here? |
36 |
> I am thinking about creating ebuild for shim. I was wondering if there |
37 |
> is any policy or suggestion where to place .efi binaries or how to |
38 |
> handle them in gentoo - it seems that there is none so perhaps there |
39 |
> should be agreed on what best practice is (install directly into |
40 |
> /boot/efi or install else and let user manually copy .efi to /boot/efi |
41 |
> or something completely different (eselect efi ...)). |
42 |
> |
43 |
> In suse default path is for example /usr/lib64/efi/: |
44 |
> ls /usr/lib64/efi/: |
45 |
> MokManager.efi elilo.efi shim-suse.efi shim.efi |
46 |
> xen-4.2.1_02-0.7.2.efi xen-4.2.efi xen-4.efi xen.efi |
47 |
> |
48 |
> yet /boot/efi contains only elilo.efi |
49 |
|
50 |
Can you even guarantee that /boot is mounted when your package is |
51 |
installed? That would be my major concern on Gentoo... |
52 |
-A |
53 |
|
54 |
>> |
55 |
>> thanks, |
56 |
>> |
57 |
>> greg k-h |
58 |
>> |
59 |
> thanks |
60 |
> |
61 |
> Martin |
62 |
> |
63 |
> |