On September 22 we released systemd v262 into the wild.
In the weeks leading up to that release (and since then) I have posted a series of serieses of posts to Mastodon about key new features in this release, under the #systemd262 hash tag. In case you aren't using Mastodon, but would like to read up, here's a list of all 35 posts:
- Post #1: Word List Based Hostname Patterns
- Post #2: Extended Attributes on Socket Inodes
- Post #3: Varlink Socket Tagging &
varlinkctl list-sockets - Post #4: Machine Tags from udev/hwdb
- Post #5:
systemd-sysupdate's installdb - Post #6: Signed
systemd-reportReports - Post #7: CLI Introspection via
--introspect-cli - Post #8: fscrypt v2 Support in
systemd-homed - Post #9: Read-Only ESP Support in
systemd-boot/systemd-stub - Post #10: Recovery Key Enrollment on First Boot & Varlink IPC for
systemd-cryptenroll - Post #11: Rogue TPM Protection for LUKS Enrollments
- Post #12: Encrypted + Verity Protected DDIs
- Post #13:
FONT_SCALE=in/etc/vconsole.conf - Post #14: Static, Single-Binary Service Manager Builds
- Post #15: Intel TDX CoCo Support in
systemd-vmspawn - Post #16: Varlink IPC for
systemd-sysinstall - Post #17:
systemd-reportas Varlink Service & New Metrics - Post #18: Sessions as Inhibitors via
pam_systemd'sinhibit= - Post #19: NvPCR Rework
- Post #20:
bootctl link-auto - Post #21:
systemd-sysupdateCompletion Hooks - Post #22:
/etc/clonetab - Post #23: Atomically Enqueuing Multiple Jobs
- Post #24: Following the Journal via Varlink
- Post #25: Coredumps via the Kernel's New Socket Protocol
- Post #26: Hardware-Suggested
systemd-sysupdateFeatures/Components - Post #27:
ActivatingConcurrencyMax= - Post #28: Restarting/Reloading Units on
confext/sysextApplication - Post #29: System Credentials for CoCo VMs in
systemd-vmspawn - Post #30: Persisting the TPM EK
- Post #31:
systemd.firstboot=headless - Post #32:
RestartRandomizedDelaySec= - Post #33:
systemd.credentials_boot_policy= - Post #34:
systemctl kexec --kernel-cmdline-reuse - Post #35: PCR Signature Policyrefs
I intend to do a similar series of serieses of posts for the next systemd release (v263), hence if you haven't left tech Twitter for Mastodon yet, now is the opportunity. My series for v263 will begin in a few weeks most likely, under the #systemd263 hash tag.
In case you are interested, here is the corresponding blog story for systemd v261, here for v260, here for v259, here for v258, here for v257, and here for v256.