Sometimes it's useful to load EFI drivers. Since loading a driver is
the same as starting it and UEFI handles cleanup after on it's own, we
can piggy back on existing chainloader command and just start the image
immediately instead of defering to "boot". Conveniently this also means
that grub can a
avnish писал(а) 24.09.2024 14:46:
> On 2024-09-22 21:30, grub-devel-requ...@gnu.org wrote:
>>
>> Message: 1
>> Date: Sun, 22 Sep 2024 13:05:07 +0500
>> From: Nikita Travkin
>> To: grub-devel@gnu.org
>> Cc: Nikita Travkin
>> Subject: [PATCH] loader/efi/chainloader: Add efidriver command
>> Messag
On 2024-09-22 21:30, grub-devel-requ...@gnu.org wrote:
Message: 1
Date: Sun, 22 Sep 2024 13:05:07 +0500
From: Nikita Travkin
To: grub-devel@gnu.org
Cc: Nikita Travkin
Subject: [PATCH] loader/efi/chainloader: Add efidriver command
Message-ID: <20240922-cmd-efidriver-v1-1-750b77bfc...@trvn.ru>
C
Hi,
please ignore my proposal about "set -e".
My assessment of "set -e" in
tests/util/grub-shell-luks-tester.in
is obviously wrong, probably because "set -e" is not inherited by
sub-shells.
The line
#! @BUILD_SHEBANG@ -e
enables script abort on command error, but causes reply
errexit
