linuxboot / linuxboot/book

Comparing kexec implementations, features

Open
#114 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
300
Forks
54
PR merge metrics
No merged PRs in 30d

Description

## implementations

| tool | language | usage |
| - | - | - |
| kexec-tools | C | Heads, Petitboot |
| systemd-kexec | C | systemd on UEFI |
| u-root (CLI+mod) | Go | Google et al |
| [kexlinux](https://github.com/im-0/kexlinux) | Rust | ? |
| [kexecboot](https://github.com/kexecboot/kexecboot) | C | ? |

## features and issues

- security
* https://people.redhat.com/vgoyal/papers-presentations/linux-plumbers-2013/vivek-linux-plumbers-conference-2013-presentation-kexec-secureboot.pdf
* https://events.opensuse.org/conferences/summitasia16/program/proposals/1166
* https://blog.cloudflare.com/linux-kernel-hardening/
- [handover](https://www.phoronix.com/news/Kexec-HandOver-KHO-Linux-MM)
- https://archive.fosdem.org/2022/schedule/event/security_seamless_kernel/attachments/slides/5061/export/events/attachments/security_seamless_kernel/slides/5061/Seamless_Kernel_Update.pdf

## references

- https://blog.linuxplumbersconf.org/2012/wp-content/uploads/2012/09/petitboot-lpc-2012.pdf
- https://www.osfc.io/2022/talks/kexec-evolutions-for-linuxboot/

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the implementations table and review the linked security, handover, and reference materials. Compare the listed kexec implementations and document their features, including resolving the ? usage entries; done when the comparison accurately represents the referenced capabilities.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, go, linux, rust
Domain
documentation, operating-systems
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.