Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create tool to check how easy it is to insert a Linuxboot kernel #282

Open
rjoleary opened this issue Aug 7, 2019 · 1 comment
Open
Assignees

Comments

@rjoleary
Copy link
Member

rjoleary commented Aug 7, 2019

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.

@rjoleary rjoleary self-assigned this Aug 7, 2019
@rminnich
Copy link
Contributor

rminnich commented Aug 7, 2019

we should be flexible enough to allow both command names right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants