[bug#41011] [PATCH] gnu: grub: Support for network boot via tftp/nfs.

[Mathieu Othacehe]

Hello Stefan,

> Yes, it’s kind of possible to inherit from grub-efi-bootloader and overwrite 
> the (configuration-file) field. In a first step this seems to work. But when 
> e.g. deleting a system generation, in guix/scripts/system.scm 
> (reinstall-bootloader) there is this code:
>
>     ;; Use the detected bootloader with default configuration.
>     ;; It will be enough to allow the system to boot.
>     (bootloader-config (bootloader-configuration
>                         (bootloader bootloader))) 
>
> It reads this information form /var/guix/profiles/system/parameters: 
> (bootloader-name grub-efi-bootloader).
> With this again the hard-coded path “/boot/grub.cfg” of is used, ignoring any 
> value overwritten in (configuration-file).

Oh, we need to fix that! It means that we would need to add a
"bootloader-configuration-file" field to <boot-parameters> record, is
that correct?

> Another issue is (install-dir (string-append mount-point "/boot")) in 
> (install-grub-efi), which ignores any (configuration-file) setting, too – 
> well, it has no access to that setting –, and implies at least “/boot” to be 
> the prefix of (bootloader (target …)). 
>
> Beside the wish to avoid this hard-coded “/boot“ assumption, I made this a 
> function with two parameters for two more reasons. 

Could it be an option to infer the bootloader installation directory and
the efi subdir from the install-grub-efi/install-grub-efi-net functions?
If TARGET is /boot-nfs/efi/Guix", could we suppose that the
boot-directory is "/boot-nfs" and the efi-subdir is "efi/Guix"?

The make-grub-efi-net-bootloader macro is a nice hack, but I fear that
it makes the bootloader configuration (even more) difficult.

Thanks,

Mathieu