also store metadata alongside content
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 196
- Forks
- 55
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 14
Description
Today we have a singular /boot/bootupd-state.json. It seems better to at least also store state alongside its content, so we'd have e.g. /boot/efi/EFI/bootupd.json as well as serializing a bit of our metadata into the BIOS partition, etc.
This would allow us to better detect situations where e.g. we happen to find an ESP from a different drive than the one holding /boot. The additional storage cost here would be minimal.
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
Start by tracing how /boot/bootupd-state.json is written and read, then identify the code handling ESP and BIOS-partition content. The issue proposes additional metadata at paths such as /boot/efi/EFI/bootupd.json. Done means state is stored alongside its content and can help distinguish an ESP from a different drive.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100