Date: Sat, 30 Jul 2016 23:51:33 -0700 From: Nathan Whitehorn <nwhitehorn@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: EFI boot: can we make loader.efi work as BOOT{x64, aa64, arm, ia32}.efi? Message-ID: <5489f1ff-d6db-c0e3-2be3-d3ae115a1f85@freebsd.org> In-Reply-To: <5bf35d8a-9941-9c6e-ea0a-20827ad26466@delphij.net> References: <5bf35d8a-9941-9c6e-ea0a-20827ad26466@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/30/16 23:20, Xin Li wrote: > Hi, > > I finally got some time to explore the UEFI boot process (kudos to > everyone who made this work!) and getting myself familiarize with the > basics. > > One quick question -- Is there some technical restriction that prevents > us from merging boot1.efi and loader.efi into one binary? > > Cheers, > No technical reason (and, in fact, when you boot from CD, that's how it works). The reason they are different is that we traditionally don't mount the EFI partition and so make installworld can't replace things there. boot1.efi is a basically static piece of code that doesn't need updates and can load loader, which does get updates, from a UFS/ZFS system. loader.efi additionally assumes that it is started from the same partition that contains the kernel, loader.conf, fstab, etc., which are also generally not on the EFI partition (except in the CD case). -Nathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5489f1ff-d6db-c0e3-2be3-d3ae115a1f85>