[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: |
Fri, 02 Dec 2011 07:53:39 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111114 Icedove/3.1.16 |
On 02.12.2011 07:22, Keshav P R wrote:
2011/11/29 Vladimir 'φ-coder/phcoder' Serbinenko <address@hidden
<mailto:address@hidden>>
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
The problem i have is installing both grub2 i386-pc and x86_64-efi .
Both have /boot/grub as $grubdir . I use /boot/grub for all grub2-bios
stuff and /boot/efi/efi/grub for all grub2-efi-x86_64 related stuff. I
have not seen any issue with having modules in <UEFISYS>/efi/grub dir
itself. AFAIK the modules are platform dependent since one can't use
i386-pc modules in i386-efi and vice-versa. x86_64-efi is out of
question since its a different arch. I guess for now doing
sed 's|/boot/grub|/boot/efi/efi/grub|g' -i grub-mkconfig
will do, until you implement the platform specific subdir idea you
mentioned. Thanks for clarifying this. For me this is not an issue.
But I also maintain grub2 packages in Archlinux. What should I tell
the users (those who have both grub2-bios and grub2-efi-x86_64), use
/boot/efi/efi/grub for everything or do the sed stuff for
grub-{install,mkconfig}?
--boot-directory=/boot-bios and --boot-directory=/boot-efi
sed 's|/boot/grub|/boot/grub-efi|g' -i grub-{install,mkconfig}
TIA.
Regards.
Keshav
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko