Valentin David 0267590c2a bootloader/assets/data/grub-recovery.cfg: set root when chainloading ...

Upstream grub does not pass to LoadImage the correct path to the
loaded binary. This results in second grub not knowing where it was
loaded from and loading the wrong grub.cfg. If we set "root", then the
path becomes correct.

Currently in mantic, the Ubuntu patch that used to be applied to 2.06
is not applied to 2.12. So we are we are back to upstream behavior.

The common use case for chainloading in EFI with grub (see
30_os-prober) always sets root. So we should do it and not get broken
again.

2023-10-11 10:16:09 +01:00

..

data

bootloader/assets/data/grub-recovery.cfg: set root when chainloading

2023-10-11 10:16:09 +01:00

genasset

many: s/ioutil.WriteFile/os.WriteFile (#13217)

2023-09-26 11:38:46 +01:00

assets_test.go

bootloader/assets: support injecting bootloader assets for tests

2021-01-25 14:53:02 +01:00

assets.go

bootloader/assets: support injecting bootloader assets for tests

2021-01-25 14:53:02 +01:00

assetstesting.go

go: go fix with 1.18

2023-09-25 13:22:14 +02:00

export_test.go

b/a: do not set console in kernel command line for arm64

2022-04-05 11:27:25 +02:00

generate.go

many: pick up special build time flags for invoking go while generating artifacts

2021-09-09 13:37:31 +02:00

grub_cfg_asset.go

bootloader: do not specify Core version in grub entry

2022-10-24 17:15:15 +02:00

grub_recovery_cfg_asset.go

bootloader/assets/data/grub-recovery.cfg: set root when chainloading

2023-10-11 10:16:09 +01:00

grub_test.go

bootloader/assets/data/grub-recovery.cfg: set root when chainloading

2023-10-11 10:16:09 +01:00

grub.go

bootloader/assets: add ttyS0,115200n8 to grub.cfg

2022-07-20 11:54:17 +02:00