UEFI vs LinuxBoot: split of config + payload
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 300
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
In UEFI, there is a split: the boot entries are stored in flash ("NVRAM"), whereas the actual payloads reside in the EFI System Partition. Those easily get out of sync.
LinuxBoot enables us to bring them together, e.g.:
Have Boot Loader Specification boot entries in the same partition as the kernels and initrds they reference.
In addition, EFI implementations would struggle with multiple ESPs, and the spec requires that removable media only have a single one.
Lots of confusion around this and clarifications are found in
https://news.ycombinator.com/item?id=16259373
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or chapter is named; start by locating the relevant LinuxBoot book section on UEFI boot entries and payloads, then review the linked Hacker News discussion for the stated confusion. Done means the book clearly explains where boot entries, kernels, and initrds reside and how LinuxBoot addresses the split and multiple-ESP concerns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100