
Don’t Get Mad, Get Triggered: 4 Home Assistant Automations I’m Finally Trying


The Genius Bar For The Free & Open Source Community


In operating systems, file systems are the foundation of stability. Users expect their storage layer to be uneventful, predictable, and above all, safe.
But behind the scenes of the Linux kernel, the development of Bcachefs—the modern Copy-on-Write (COW) file system slated to compete with Btrfs and ZFS—has been anything but boring.
Following a series of heated standoffs between Linus Torvalds and Bcachefs lead maintainer Kent Overstreet, the Linux creator made a dramatic executive decision: Bcachefs has been dropped from the mainline Linux kernel.
This conflict highlights the tension between rapid, visionary development and the strict discipline needed to manage software for billions of devices worldwide.
Merged into the mainline Linux kernel late in 2023, Bcachefs was hailed as the next-generation file system for the Linux ecosystem.
For years, Linux users have faced challenges with advanced storage features:
Bcachefs promised to bridge this gap with a high-performance, feature-rich, Copy-on-Write design. Its message was simple: “The file system that doesn’t eat your data.” It brought snapshotting, encryption, multi-drive management, and ZFS caching directly into Linux.
The breaking point did not occur because of a bug. It occurred because of a fundamental breach of the Linux kernel’s development protocol.
During the release cycle, kernel development follows a strict, consensus-based timeline:
1. The Merge Window: A two-week period where new features, drivers, and subsystems are merged into the upcoming kernel version.
2. The RC Phase: Code is frozen; developers may only fix bugs and regressions to ensure release stability.
During the RC phase, Kent Overstreet submitted a pull request containing a major change called “journal-rewind.” The feature was designed to improve Bcachefs’ repair and recovery functionality—a highly sensitive part of any file system.
Linus Torvalds objected. Introducing a structural change to journaling during the RC phase violates the kernel’s core safety rules.
Theodore Ts’o, the long-time maintainer of the robust ext4 file system, also weighed in. He pointed out that modifying journaling code so late in the cycle risks introducing severe, unpredictable regressions that could destroy user data—the exact opposite of what a file system is supposed to do.
The debate quickly devolved from a technical discussion into a clash of development philosophies.
Kent Overstreet argued that rules should be flexible when fixing data integrity. He felt delivering critical recovery features outweighed following the standard timeline, claiming Bcachefs needed more agility than traditional file systems like ext4.
Torvalds and Ts’o countered with a different reality: the rules are what protect user data.
In Linux’s vast ecosystem, a regression in a core file system can brick servers and corrupt data. Strict merge windows are crucial safety gates, proven over decades.
After a tense back-and-forth, Overstreet resubmitted the patch, arguing that other file systems, such as XFS and Btrfs, had been granted similar flexibility in the past.
Linus merged the patch to unblock the immediate release, but reached his limit. He made it clear that because Overstreet rejected the consensus-based rules of kernel development and refused to accept standard oversight, Bcachefs could no longer remain in mainline Linux.
Torvalds officially dropped support for Bcachefs, parting ways with the filesystem.
The removal of Bcachefs from the mainline kernel is a significant setback for the project, influencing not only its immediate trajectory but also shaping how future filesystems might approach kernel integration and community process.
Bcachefs will now be maintained “out-of-tree,” as ZFS is. Developers must package and compile modules for each release, which creates friction for users because Bcachefs won’t work natively with standard distributions.
Mainstream distributions are unlikely to support filesystems not in the mainline Linux kernel. Bcachefs will likely be limited to homelabbers, power users, and custom distributions.
This incident reinforces the authority of mainline kernel maintainers and sets a precedent for how future contributors should navigate development protocols. It signals to all developers that adherence to established processes will remain essential for the inclusion and long-term success of new filesystems in Linux.
The Bcachefs drama is a tragedy of open-source engineering. Bcachefs is a brilliant, highly innovative filesystem that solved problems other filesystems spent decades avoiding.
But in enterprise and system-level software, how you build is just as important as what you build.
The Linux kernel is the most successful collaborative software project in human history because it prioritizes safety, discipline, and consensus over individual speed. When a developer refuses to play by those rules, the system self-corrects—even if it means losing some of the most promising storage technology of the decade.
Support stable systems, open standards, and the rigorous engineering that keeps our digital world running.

Welcome, 2026! This year I’m going to get my hands a little dirtier by shifting from theory-heavy exploration into something more concrete: real hardware, real experiments, real mistakes—and the lessons that come from all of it.
This year started with three repurposed Lenovo 720q Tiny PCs. They’re not new; in fact, they’re e-waste from my job, since they’re too old to upgrade to Windows 11. But they are more than capable of becoming something useful!
So I did what any Linux enthusiast with curiosity and a desire to set up a home lab would do. I turned them into a Proxmox cluster.
I’ve written about Linux systems from the perspective of a daily driver: desktops, workflows, tools, and configuration. But increasingly, my curiosity has shifted more towards infrastructure—how systems run behind the scenes.
Proxmox sits at an interesting intersection:
Rather than reading about Proxmox in the abstract, I wanted to learn it the only way that really sticks: by building something real and seeing what breaks.
The cluster itself is modest:
I plan to write about
This won’t be a polished “how-to guide from an expert.”
It will be a learning journal—documenting what works, what doesn’t, and why.
There’s a lot of Proxmox content online. Much of it assumes:
That’s not how I learn, and it’s not how I want to write.
This year at Einstein’s Saloon, you’ll see:
If you’re curious about Proxmox but intimidated by it, this series is for you.
Alongside virtualization, another hands-on tool has become a bigger part of my daily tech life: 3D printing.
While it may not look like traditional Linux territory at first glance, 3D printing fits naturally into the same mindset:
In 2026, I’ll be writing about:
I won’t be writing about flashy figurines, but about useful, repeatable outcomes—the same philosophy that drives everything else here.
This year, the site will lean into:
Less “perfect setups” and more “here’s what actually happened.”
Einstein’s Saloon remains the genius bar for the free and open-source community, but in 2026, the genius will look a little messier.
If you’re interested in
Then you’re in the right place.
Pull up a stool; let’s build, break, and learn together in 2026!
Graphical interfaces come and go, but the command line is forever—and in 2025, the Linux CLI scene is more intelligent and more capable than ever. Whether you’re managing servers or just trying to get things done faster, the right terminal tools can upgrade your entire Linux experience.
Here are five powerful CLI tools that deserve a permanent place in your toolkit this year.
If you still rely on plain grep for searching code, configs, or system files, it’s time to try ripgrep. Ripgrep (rg) is a modern drop-in replacement for grep.
Why It’s Great
fzf is a fuzzy finder for the command-line. The longer you use it, the more you wonder how you lived without it.
What It Can Do
cat is fine, but bat is better. It’s a drop-in replacement that adds modern features without changing your workflow.
Features
Bonus: Works beautifully with ripgrep and fzf for a hyper-efficient terminal workflow.
ls gets the job done, but eza (formerly exa) gives you a more readable view of your file system.
What You Get
Why You’ll Love It
Directory browsing will feel fun.
Fastfetch is the spiritual successor to Neofetch—rewritten for performance, aesthetics, and modern systems.
Highlights
Perfect For: Showing off your Linux setup.
Zoxide: A smarter cd that learns your frequently used directories.
fd: A modern replacement for find—fast, intuitive, and colorized.
The Linux command line isn’t just a place to type commands—it’s a launchpad for automation, efficiency, and mastery. These five tools make Linux faster, more powerful, and more enjoyable in 2025.
[{.alignleft}](/wp-content/uploads/2025/11/NixOS-Icon-02.png)
For years, Linux enthusiasts, **including myself**, have chased the “perfect distro.” Some want stability. Some want bleeding-edge packages. Some want reproducibility. And some—let’s be honest—just want something cool to tinker with at 2 a.m.
But **NixOS** quietly sidesteps this entire debate. It doesn’t compete with Ubuntu, Fedora, or Arch in the traditional sense. Instead, it **redefines what a Linux distribution can be**. We warned, **NixOS does have a steep learning curve**, but if you haven’t tried it, you’re missing one of the most transformative distros in modern computing.
## A Paradigm Shift, Not a Distro Hop
Most distributions configure the system through a web of package managers, shell scripts, and config files. NixOS ignores all of that and says: *”What if your entire system was a single, declarative, version-controlled document?”*
With NixOS, your system _is_ code. Not metaphorically, but literally. One file (*configuration.nix*, or a *flake*) describes:
– Installed software
– System services
– Users and groups
– Networking
– Hardware support
– Desktop environment
– Custom system tweaks
Change the file → rebuild the system → done.
If you can manage a Git repo, you can manage your entire OS.
## Reproducibility: The Superpower Other Distros Wish They Had
Imagine the following scenario: You set up the perfect workstation, terminal tools, development environments, fonts, and drivers. Then your SSD dies. Typically, you’d spend hours reinstalling.
On NixOS: **Git clone → nixos-rebuild switch → your entire system is back.**
Not just installed packages—the **entire configured system**, down to the kernel modules and systemd services.
## Below are some reasons why NixOS has a cult following among:
– DevOps engineers
– Software developers
– Homelabbers
– HPC folks
– Tinkerers and power users
### The Nix Package Manager
Nix, the package manager behind NixOS, is a beast—beautiful, powerful, and occasionally intimidating.
Here’s why it matters:
#### 1. Atomic upgrades
If an update breaks something, you can roll back your entire system in seconds.
#### 2. Zero dependency hell
Packages are built in isolated environments, so no more:
– Library conflicts
– Version clashes
– ABI breakage
– “This requires Python 3.12, but your system is on 3.11.”
#### 3. Multiple versions of the same software
Need Python 3.10 **and** Python 3.12?
Need two versions of Node?
Want three versions of GCC?
*No problem with Nix.* This flexibility makes NixOS feel like Linux in cheat mode.
## Home Manager: Your Dotfiles, Evolved
If NixOS handles system configuration, **Home Manager** handles user-level configuration—dotfiles, packages, shells, editors, theming, and more.
Home Manager lets you:
– Version-control your dotfiles
– Reproduce them on any machine
– Avoid “dotfile drift” across systems
– Switch between laptops/workstations effortlessly
Example:
home.username = {
programs.zsh.enable = true;
programs.starship.enable = true;
home.packages = [ pkgs.fastfetch pkgs.bat pkgs.exa ];
};
Rebuild → your environment is instantly standardized.
##### Home Manager is so good that even non-NixOS users install it. But on NixOS? It’s a match made in config-management heaven.
## Flakes: The Future of NixOS (and Why You Should Care)
Flakes add:
– Inputs (like package sources)
– Outputs (like your system config)
– Pinning (so updates never surprise you)
– Reproducibility across machines
Example:
nixosConfigurations.nixos = { system = “x86_64-linux”; modules = [ ./configuration.nix ]; };
Flakes lets you share your system between machines, maintain multiple configurations, and track changes.
## Why NixOS Feels Like Magic for Power Users
You’ll love NixOS if any of these statements hit home:
– “I want my whole system in Git.”
– “I want to rebuild a machine in 10 minutes.”
– “I’m tired of fixing dependency issues.”
– “I want the same environment on every machine.”
– “I want to understand _exactly_ how my system is built.”
NixOS gives you **control without chaos**, **flexibility without breakage**, and **power without fragility**.
## The Learning Curve: Real but Worth It
NixOS isn’t plug-and-play like **Pop!OS** or **Linux Mint**.
You will have to:
– Read docs
– Learn the Nix language
– Debug your configuration, and
– Occasionally mutter “Why isn’t this service starting?”
But once you get past the initial bump, something flips in your brain. You realize: *”This isn’t just a distro, but a better way to run computers.”*
## So, why haven’t you mastered it yet?
Not because it’s too hard—because it’s too _different_.
It asks you to let go of the old way of managing Linux.
But if you’re a Linux enthusiast, a sysadmin, or anyone who wants a smarter, reproducible, future-proof workflow, then NixOS isn’t just worth learning—it’s essential.
## Final Thoughts
I believe **NixOS** is the most important distro you haven’t mastered yet because it represents the next evolution of Linux use. Declarative systems, reproducibility, atomic upgrades, isolated builds, multiple versions, and Git-managed everything.
NixOS doesn’t just add features; it solves problems other distros have lived with for decades.
If you want a Linux environment that’s efficient, elegant, and engineered for power users, it’s time to give NixOS the attention it deserves.
And as always—welcome to the Saloon. Pull up a stool, grab a coffee, and let’s build your next great Linux system together!