16.02.2016 07:11, Michael Chang пишет: > On Sat, Feb 13, 2016 at 10:29:58AM +0300, Andrei Borzenkov wrote: >> 12.05.2015 18:22, Michael Chang пишет: >>> On Tue, May 12, 2015 at 02:57:00PM +0300, Andrei Borzenkov wrote: >>>> В Tue, 12 May 2015 18:52:22 +0800 >>>> Michael Chang <mch...@suse.com> пишет: >>>> >>>>> On Fri, May 08, 2015 at 09:53:41PM +0300, Andrei Borzenkov wrote: >>>>>> There are two main applications. >>>>>> >>>>>> 1. Omit install device to create generic image intended for chainloading >>>>>> from other master loader. Such image can be put on any device (or file >>>>>> system) and will still be able to find its $root. Currently even with >>>>>> --no-bootsector grub-install optimizes image by skipping UUID search if >>>>>> possible. >>>>>> >>>> >>>> Actually I think it is useful for all platforms. >>> >>> As it works across all platform, os-prober should consider chanloading >>> core images if possible rather than digging into grub configs. Is there >>> any plan for that ? >>> >> >> At least on EFI it is not possible to chainload GRUB from /boot until it > > I'm skeptical to this. From what I know it's possible because grub's efi > chainloader reads efi image via it's own filesystem support, so that it > did not limited by what firmware could offer. And LoadImage can accept > SourceBuffer as an option to pass the pointer of loaded image buffer > directly. > > Honestly I didn't really test it, but glancing at the source code it > sounds promoising to work to me. >
Yes, indeed. I'm not sure what went wrong last time I tried it; I had problem with device path. Still, this is core.img vs. core.elf, which means it is platform dependent.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
