a dedicated chapter on `kexec`
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 62/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- linux
- Domain
- documentation, operating-systems
Research direction
Start by reading the related issue #114 and the referenced Ubuntu and Arch Linux kexec man pages. Build a dedicated chapter covering security notes, purgatory, both kexec syscalls, userspace tool differences, device-tree handling, and the listed documentation gap; done means these facets are clearly explained in the book.
Written by the indexing model from the issue text.
Description
Our beloved syscall(s) and corresponding userspace utilities have so many facets, we can hardly add them to the tools evaluation page, so let's create a dedicated chapter. A few things I would initially add:
-
security notes
-
purgatory
-
difference between
kexec_loadandkexec_file_load -
differences between various
kexecuserland tools- What does one do over the other?
- Recurring issue with new kernel not getting a new DT
-
https://manpages.ubuntu.com/manpages/focal/man2/kexec_file_load.2.html does not even mention device tree btw
-
https://man.archlinux.org/man/kexec.8.en has it:
--dtb=file
Specify device tree blob file. Not applicable while using --kexec-file-syscall.
Consider this the second part of https://github.com/linuxboot/book/issues/114
- Dominant language
- JavaScript
- Stars
- 300
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from linuxboot/book
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
automation models
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
needs:triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
enhancement status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
mastra-ai/mastra#25508 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 72/100
githubnext/gh-aw-cao#15017 ·
Maintainers usually reply within 1 day