On 9 January 2017 at 20:35, Kevin Buckley <[email protected]> wrote:
As regards this bit. > * The need to have to add an > > efivarfs /sys/firmware/efi/efivars efivarfs defaults 0 1 > > line into Chapter 7's /etc/fstab, may not be necessary (?) as that > directory was created on an LFS system that didn't have such a line. I don;t fully understand what's going here, however 1) if the LFS system is booted from within an non-LFS Grub (one of mine was from Fedora 21) that allows for the kernel to be specified using that Grub's "linuxefi" attribute, so linuxefi /path/to/kernel root=/path/to/root ro then you don;t appear to need the /etc/fstab line, and indeed, you'll get told during the boot that the mounter knows nothing about the efivars filesystem type. Howwver, LFS's efibootmgr will still be capable of interrogating your UEFI environment. Presumbly this is related to the "EFI handover" message that was seen before. 2) If the LFS system is booted from the LFS+Hint's grub, so using linux /path/to/kernel root=/path/to/root ro then, unless you have the efivars filesystem mounted, and you are able to, then LFS's efibootmgr will be NOT capable of interrogating your UEFI environment, and you'll be told that there is no efivars filesystem Hope that's useful. -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
