I would be less competent than you would want for a lead, but I would be glad
to help out on boot loaders. I'm familiar with for about, UEFI and legacy
BIOS.--CharlesSent from my T-Mobile 4G LTE device------ Original
message------From: Bruce Dubbs via lfs-dev Date: Wed, Aug 5, 2020 9:51 AMTo:
lfs-dev@lists.linuxfromscratch.org;Cc: Bruce Dubbs;Subject:Re: [lfs-dev] grub
with uefi for LFS 10?On 8/5/20 2:25 AM, Xi Ruoyao via lfs-dev wrote:
> On 2020-08-05 14:37 +0800, Kevin Buckley via lfs-dev wrote:
>> On Mon, 3 Aug 2020 at 00:46, Xi Ruoyao via lfs-dev
>> wrote:
>>> It's nearly impossible. If we do that we'll have to introduce at least five
>>> new
>>> packages: dosfstools, popt, pciutils, efivar, and efibootmgr. Pciutils is
>>> recommended to be installed along with "which" (it's a package's name), and
>>> one
>>> of wget/curl/lynx to make update-pciids script usable. And, to make grub
>>> menu
>>> "showing normal" we'll need freetype. Freetype has a circular dependency
>>> with
>>> harfbuzz. Harfbuzz requires glib, graphite, and ICU to be fully functional.
>>>
>>
>> Worth pointing out, as the hint does, that you can install Freetype
>> without the harfbuzz, so as to get enough to install an enhanced
>> Grub, and then go back and install a Freetype+harfbuzz later.
>
> That's my approach, and OK for a hint.
>
> Another way: provide a binary unicode.pf2 file on Anduin, and skip freetype.
> It's just a font and it's not a problem not to build a font "from scratch".
>
>> Similarly, the lack of an update-pciids script may not be a major
>> problem as, when building the UEFI-aware Grub for the first time,
>> you can download what that script would fetch, using the host
>> system, and just put the payload into place on the LFS system.
>
> The problem is we have to defer the activation of update-usbids.timer (for
> systemd) or cron job (for sysv) after wget/curl/lynx is installed. Then where
> should we put the instruction? Not a technical problem but a book structure
> issue.
>
>> It's probably way too far beyond LFS to have it in the LFS Book,
>> but the basic capabilities are not as hard to add as one might
>> come to think, just by following all of the BLFS Book's dependencies
>> to the end of each chain.
>
> I think it might be better to put EFI grub and its dependencies into BLFS.
> There
> is BLFS #5379 (opened 6 years ago). If Bruce agrees I'll change the milestone
> to 10.1 (10.0 will be too hurry) and do it. And, William Harrington suggested
> that LFS should support some non-x86 architectures, which would require
> different bootloaders. They can be put into a new BLFS chapter "alternative
> bootloaders", along with EFI grub.
If you can maintain it on an ongoing basis, I'm OK with adding a section
on bootloaders in 10.1. I went ahead and added a 10.1 milestone to BLFS.
When you are ready, we can discuss where it should go in the book.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
