You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given a UEFI image as input, this tool quantifies how easy it is to insert and debug a LinuxBoot kernel. Here is a starting list of rules which can be easily checked:
Rule
Description
Allowed Firmware Volumes
At most 4 firmware volumes are allowed: PEI, UEFI (DXEs, APPs, etc.), NVRAM, NVRAM backup
No Misplaced Files
The PEI firmware volume may not contain any DXE blobs. The DXE firmware volume may not contain any PEI blobs.
Free Space
The DXE Firmware Volume must have at least 8 megabytes of uncompressed free space.
Compression Method
The firmware volume containing DXEs is either uncompressed or compressed with standard LZMA compression. The protocol GUID for LZMA compression is EE4E5898-3914-4259-9D6E-DC7BD79403CF.
GUID Names
Prefer that DXEs contain a descriptive name in their USER_INTERFACE sections.
When a rule fails, the output describes which rule failed and what can be changed to fix it.
I don'd know what the best name for the command should be, but something like "linuxboot-readiness-check" or "lbrc" could work.
The text was updated successfully, but these errors were encountered:
Given a UEFI image as input, this tool quantifies how easy it is to insert and debug a LinuxBoot kernel. Here is a starting list of rules which can be easily checked:
When a rule fails, the output describes which rule failed and what can be changed to fix it.
I don'd know what the best name for the command should be, but something like "linuxboot-readiness-check" or "lbrc" could work.
The text was updated successfully, but these errors were encountered: