ISSUE concerning configuration of UEFI boot                                       16 June 2023 GLF
---------------------------------------------------------------------------------------------------

Thie current live-build configurations for 800 series GLF prepared OS builds contains a problem which must be addressed manually (for now) at build time.  Under config/includes.binary/boot/grub/ the file "grub.cfg" is placed to force the boot process for EFI to match the Legacy Boot options.  However, to get this, there is a file name dependency in the EFI version (grub.cfg) which does not happen in the isolinux version (Legacy boot).


Example of menuentry under grub.cfg file under config/includes.binary/boot/grub/:

   # Live boot
   menuentry "Live system (amd64)" --hotkey=l {
	   linux	/live/vmlinuz-6.1.0-9-amd64 append noprompt cdrom-detect/try-usb=true 
                boot=live components nottyautologin splash persistence findiso=${iso_path}
       initrd	/live/initrd.img-6.1.0-9-amd64
   }


NOTE that the above menu entry refers to the Linux boot file BY NAME (/live/vmlinuz-6.1.0-9-amd64)

This name must be EDITED in EVERY menu entry for EVERY BUILD of the OS until a workaround is developed, or else the "grub.cfg" file must be eliminated altogether from the configuration.  Eliminating the "grub.cfg" file from the configuration fileset will cause the default package version to be installed, which will always have the correct linux image name, but will not have the desired boot parameters.

However, the correct image name will CHANGE with every update to the Linux system files (frequently).

It is not known before the build what the image name will be, because the latest version in the repository at build time will be used, and that is not known by the default live-build script. 
However, it can be surmised just before the build time that the repository contains the valid name for the latest version, and that can be inspected with Synaptic just before the build.  Unless an upgrade occurs between the beginning if the build and the actual build, that should be correct.


HOW TO FIND LATEST AVAILABLE VERSION:

It is assumed you are booted with the same or compatible OS version (ex. 800 series GPERS) and CPU type (686, amd64) for the build configuration.


PATCH grub.cfg manually:

Edit the grub.cfg file.  You will find menu entries containing entries like:
   
   vmlinuz-6.1.0-7-amd64
   
Use Synaptic, reload packages, then look for Installed Packages, "linux-image".  You should find the currently installed linux image version (Ex. linux-image-6.1.0-9-amd64) and its latest available version (may be different, Ex: 6.1.27-1).  Use the PACKAGE name to edit the "grub.cfg" file to ensure the latest bootable image will be used in the EFI boot (Ex. vmlinuz-6.1.0-9-amd64 and initrd.img-6.1.0-9-amd64).  Edit ALL such references.

  
FOR NOW, AVOID THIS METHOD

Because the above must be manually patched and is problematic as upgrades inevitabley occur, avoid it while maintaining the grub.cfg file itself ny renaming the "boot" folder to "notboot".
  
