flowey: report size of initramfs/initrd in build processes, and how large each item is.
Open
Nobody has claimed this yet.
bug
CI
flowey
- Dominant language
- Rust
- Stars
- 1.9k
- Forks
- 238
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 100
Description
I'd like to see how large our initrd is, i wonder if the debug binsize even stripped, is huge now.
Originally posted by @chris-oo in https://github.com/microsoft/openvmm/issues/2407#issuecomment-3529746353
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 locating the flowey build process that creates the initramfs/initrd. Define completion as reporting the total image size and the size of each included item, including enough information to assess whether debug binaries are stripped; the issue names no specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, operating-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100