[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH, RFC, RFT] Mactel integration

From: Vladimir 'φ-coder/phcoder' Serbinenko
Subject: Re: [PATCH, RFC, RFT] Mactel integration
Date: Tue, 29 Nov 2011 10:00:38 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20111114 Icedove/3.1.16

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

Vladimir 'φ-coder/phcoder' Serbinenko

reply via email to

[Prev in Thread] Current Thread [Next in Thread]