351de38e4b
Apparently some firmwares don't allow us to write this token, and refuse it with EINVAL. We should normally consider that a fatal error, but not really in the case of "bootctl random-seed" when called from the systemd-boot-system-token.service since it's called as "best effort" service after boot on various systems, and hence we shouldn't fail loudly. Similar, when we cannot find the ESP don't fail either, since there are systems (arch install ISOs) that carry a boot loader capable of the random seed logic but don't mount it after boot. Fixes: #13603 |
||
|---|---|---|
| .. | ||
| efi | ||
| bless-boot-generator.c | ||
| bless-boot.c | ||
| boot-check-no-failures.c | ||
| bootctl.c | ||