Hi, I do think it's important to support installation of the efi boot application in one place but modules (prefix) in another. That scenario makes sense, at least, for oses that store the prefix on redundant file systems/abstractions.
--S On Nov 28, 2011, at 11:25 PM, Keshav P R <the.ridikulus....@gmail.com> wrote: > On Tue, Nov 29, 2011 at 12:04, Seth Goldberg <seth.goldb...@oracle.com> wrote: > > On Nov 28, 2011, at 2:23 PM, Vladimir 'φ-coder/phcoder' Serbinenko wrote: > > > On 28.11.2011 14:25, Vladimir 'φ-coder/phcoder' Serbinenko wrote: > >> Hello all. Based on the information from > >> http://mjg59.dreamwidth.org/7468.html I intend to add support for such > >> install. It requires a small HFS+ volume mounted at /boot/mactel. I also > >> simplify handling of EFI directories by adding explicit option to specify > >> it and removing some "compatibility" kludges (they don't make anything > >> compatible with anything since "old behaviour" was mostly not to install > >> at all) which made the code in question difficult to maintain. Patch > >> attached and branch "mactel" pushed. > > Now attached the right patch. > >> I've tested only as far as to see the appropriate directory structure in > >> place. Can anybody test it on real mac? > >> > > > > The only thing I'd suggest, after some more thought, is to remove > --efi-directory and just use the install_device (the non-option arg given to > grub-install) as the EFI directory -- this is also most-consistent with the > usage a user might expect (IMHO). > > The --efi-directory option does same thing as --root-directory option for > specifying mountpoint of UEFISYS partition. At first I thought grub-install > now allows specifying the EXACT directory where all the files aka grub.efi , > *.mod and grub.cfg should exist. > > From my understanding of how grub-install works, if I specify > > --efi-directory=/boot/efi --bootloader-id=grub2 > > 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 use > > --efi-directory=/boot/efi --boot-directory=/boot/efi/efi --bootloader-id=grub > > Even if I use > > --efi-directory=/boot/efi --boot-directory=/boot/efi/efi --bootloader-id=grub2 > > I get /boot/efi/efi/grub/{core.efi,*.mod} and /boot/efi/efi/grub2/grubx64.efi > . Is there any option to specify to exact dir (both for grub-install and > grub-mkconfig and other related scripts which use --boot-dir and --root-dir)? > > I don't know whether it is okay to compare grub2 with syslinux, but extlinux > provides --install option to specify the directory where ALL syslinux related > files are present, no --root-dir , --boot-dir , --bootloader-id confusion. I > want all files under one dir (/boot/efi/efi/grub2, not referencing to > /boot/grub or /boot/efi/efi/grub). Thanks in advance. > > Regards. > > Keshav > > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel
_______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
