mkosi-initrd in Fedora
summary
mkosi-initrd builds initrds directly from distro packages (a simple 20-line config that lists packages), uses mks 15/mkosi to produce cpio initrds unprivileged, and uses systemd in initrd so no extra init-script glue is needed. Images become reproducible and signable for Koji/unified kernel workflows; kernel modules currently include the full modules RPM (~30 MB) but planned filtering and extensions let signed overlays and TPM/ESP-encrypted credentials add local changes.
AI-written summary · about
chapters (17)
- 0:00mkosi-initrd in Fedora
- 2:28Traditional initrd limitations
- 6:26mkosi-initrd simplifies initrd
- 8:34Building initrd from distro packages
- 13:38Size and content of mkosi-initrd
- 17:36Local modifications and variants
- 19:01Secure credentials in initrd
- 21:12Systemd extensions for initrd
- 24:51Kernel installation integration
- 26:39Progress and future outlook
- 28:31Q&A: Building initrd without privileges
- 29:43Q&A: Rebuilding initrd for changes
- 30:48Q&A: Kernel module selection
- 31:57Q&A: Special hardware in extensions
- 33:24Q&A: Matching extensions to kernels
- 34:52Q&A: Kernel installation responsibility
- 35:14Demo: Configuring mkosi-initrd
related talks
39mNew design for initrds
43mTowards Secure Unified Kernel Images for Generic Linux Distributions and Every...
35mHardening OS Distribution: Verifiable and sealed OS with bootc and composefs
28mBuild System Analysis for Kernel Development and Customization
01h 05mImmutable and Stateless Systems with systemd
23mCreate your own custom Fedora IoT images
19mLinux on RISC V Fedora and Firmware Status Update
24mIntroducing Fedora KDE