Is Fedora's Default Btrfs Compression Right for Your Workload?
Fedora enables Btrfs zstd compression by default, but the practical decision is whether to keep it, tune it, or disable it. Here is how to measure and decide.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Fedora enables Btrfs zstd compression by default, but the practical decision is whether to keep it, tune it, or disable it. Here is how to measure and decide.
Deploy a lightweight Fedora microservice that starts automatically on first socket connect, stays unprivileged, and is protected by SELinux. This guide shows the minimal unit file, trust boundaries, health checks, and how to handle common failure modes.
Decide the right SELinux mode for your Fedora system. Compare Enforcing, Permissive, and Disabled, understand trade‑offs, and follow a step‑by‑step guide to switch and validate your choice.
Learn why Fedora Workstation uses Btrfs by default, how its subvolume layout enables instant system snapshots, and what trade‑offs to watch when managing space and performance.
DNF already prunes cached packages and can erase orphaned dependencies. The real work is checking which settings are in force on your Fedora release before adding cleanup scripts.
Fedora Workstation uses Btrfs by default, offering cheap snapshots and GRUB-based rollbacks—but the root-versus-home subvolume split means you need to snapshot intentionally.
Fedora upgrades that stall on dependency conflicts usually come down to two DNF flags: --best enforces strict upgrades, --skip-broken defers problem packages. Here's how to use each without leaving your system half-upgraded.
When GNOME on Fedora boots to a black screen or falls back to X11, this guide covers DRM driver issues, GPU driver misconfiguration, SELinux policy blocks, compositor errors, and XWayland resource limits with ordered checks and fixes.
Fedora Silverblue and Kinoite use rpm-ostree and OSTree to deliver whole OS images atomically. Updates stage a new bootable deployment, so a failed upgrade cannot corrupt the running system and rollback is built in.