Exercise 2: Why Fedora's Btrfs Default Follows From Its Own Release Model — Possible Solution ==================================================================== WHAT CHAPTERS 3 AND 7 ALREADY ESTABLISHED ABOUT FEDORA ------------------------------ Chapter 3 established Fedora as a fast-moving distribution with a roughly 6-month release cadence; Chapter 7 placed Fedora further toward the "fast cycle" end of the stability-vs-freshness spectrum, meaning Fedora systems change - and receive updates - more frequently than a point-release or enterprise system. WHAT BTRFS SPECIFICALLY OFFERS, PER THIS CHAPTER ------------------------------ Per this chapter, "Btrfs's own cheap, built-in snapshot capability makes rolling back a failed update dramatically easier than it would be on ext4." Btrfs can take a near-instant, low-cost snapshot of the filesystem's current state before applying changes, and revert to that snapshot quickly if something goes wrong - a capability ext4 simply doesn't offer natively. WHY THIS CONNECTS DIRECTLY TO FEDORA'S OWN UPDATE FREQUENCY ------------------------------ Per this chapter, "a distribution that changes more often genuinely benefits more from cheap, built-in rollback than one that rarely changes." A system receiving updates frequently has proportionally more opportunities for any single update to introduce a problem - having a cheap, reliable way to undo a bad update matters more the more often updates happen. A system that changes rarely (like RHEL, per Chapter 7's own spectrum) has fewer such moments where rollback capability would even be exercised. WHY THIS ISN'T AN ARBITRARY TECHNICAL PREFERENCE ------------------------------ Per this chapter, "Fedora's own default filesystem choice is a direct, sensible consequence of its own release-model identity, not an arbitrary preference." The choice of Btrfs specifically serves Fedora's own already-established identity as a fast-cycle distribution - it's not a filesystem chosen in isolation, but one chosen because it specifically mitigates a risk that Fedora's own release cadence makes more relevant than it would be for a slower-moving distribution. WHY THIS WORKS AS AN ANSWER ------------------------------ It connects Fedora's fast-cycle identity (established in Chapters 3 and 7) directly to Btrfs's own snapshot/rollback capability using this chapter's own reasoning, and explains why more frequent updates specifically increase the practical value of that capability, making the filesystem choice a logical consequence rather than an unrelated decision.