New design for initrds
summary
Proposal replaces custom initrd scripts with systemd-based images built by mkosi, producing a compressed CPI initrd plus per-feature system extensions as GPT images with a filesystem, dm-verity data and JSON signatures verified by the kernel. Builds use distro package managers (dnf/apt) so images are reproducible and signed with TPM-backed credentials; current prototype runs on laptops, modules make up about half the initrd and overall images are ~20% larger, distro integration still missing.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:27Goals and complexity
- 5:01Reusing systemd in initrds
- 7:11System extensions concept
- 10:43Building initrds with mkosi
- 13:57Integration with distributions
- 16:54Reproducible and signed builds
- 20:06Transition vs extension
- 23:41Overlaying root filesystem
- 27:20Kernel coupling and rebuilds
- 31:17Current initrd size and firmware
- 33:04Fedora adoption timeline
- 35:34Packaging and dependencies
- 36:59Secure Boot and signatures
- 38:26Q&A
related talks
36mmkosi-initrd in Fedora
01h 05mImmutable and Stateless Systems with systemd
19mSubsystem Update: Linux Integrity Status Update
26mIntegrity
35mHardening OS Distribution: Verifiable and sealed OS with bootc and composefs
01h 01mDiskless Booting of RPi 400 Using Bootp, tftp, iscsi and NFS
47msystemd and TPM2
40mAn Operating System of Our Own
