The freedom to build whatever you want.
This is my brain dump. Decades of building infrastructure, distilled into a tool and a philosophy. The BSD community got ZFS right. Linux got hardware support right. BSD has jails. Linux has containers. Different implementations of the same ideas, each with strengths the other lacks.
kldloadOS exists to empower you to build whatever you like — with a secure-by-default attitude, the highest expectations for quality, resilience, and reliability, and a focus on repeatability, speed, and recovery. If it doesn’t meet those expectations, it goes in the trash.
This isn’t a product pitch. It’s an invitation. Take the tools. Build something. Break it. Snapshot it. Roll it back. Ship it. Replicate it. The freedom is yours.
What this is really about
Kernel Architecture
Monolithic vs. microkernel vs. hybrid. Not as an academic exercise — as a practical skill. When do you need real isolation? When is a container enough? When should you reach for a VM? When is eBPF the answer? These are engineering decisions, not religious ones.
Filesystems as Infrastructure
Why ZFS. Why not btrfs (yet). Why ext4 is fine until it isn't. What copy-on-write actually means for your data. How snapshots work at the block level. How boot environments change the game. The stuff that makes you dangerous in the best way.
Systems Communication
TCP vs. UDP. Active vs. passive. Request-reply vs. pub-sub. Why FTP uses two channels. Why ZeroMQ exists. Why Salt uses a message bus and Ansible uses SSH. Control planes, data planes, back channels. The patterns that make distributed systems actually work.
The Right Tool for the Job
Stop using what's popular. Stop using what someone on YouTube recommended. Use what's correct. Linux containers for speed. VMs for isolation. ZFS for data integrity. eBPF for observability. Microkernels for safety-critical systems. Every tool has a purpose. Know the purpose.
The Unix philosophy manuals are dusty. They're not wrong.
"Do one thing well." "Everything is a file." "Text streams are a universal interface." These ideas are fifty years old and more relevant than ever. But they're buried under layers of hype, abstraction, and "just use Kubernetes."
We're not here to gatekeep. We're not here to tell you the old way is the only way. We're here to dust off the manuals, add the things we've learned since, and hand them to anyone who wants to understand how computers actually work. Because the people who understand the fundamentals build things that last. And the people who don't keep rebuilding the same broken thing on a new framework every two years.
kldload is a starting point. An ISO that gives you ZFS on Linux done right. A codebase you can read and understand. And a growing library of explanations for people who want to know why, not just how.
This is free. This is open. This is for everyone.