QSOE Development Blog

QSOE is built every day on Debian. The 0.4 release was tested from a fresh clone on Debian too, and that's exactly the problem: a build that has only ever seen one distro silently learns that distro's habits. So on Monday evening, a day after the 0.4 release, I tried something different: a brand-new Azure Linux 4.0 virtual machine in QEMU, an 8 GB disk, a minimal install, and nothing else. RPM packages, tdnf , no apt anywhere. The rule for the evening was simple: clone, type make , and write down every single thing that breaks. I had Claude Code keep the log while I typed the errors in. The obvious ones A minimal image really is minimal. Before the first line of QSOE was compiled, I had installed git , make , wget , tar , pip3 and, a bit later than I should have, the host gcc . None of that is surprising. What was pleasant: xz , mtools , dosfstools and cpio were already there. The seL4 side of the build has a host check that lists everything it needs in one go. It ...

QSOE 0.4 is out today. In component terms: Component What it is 0.3 0.4 nq QSOE/N — the Skimmer microkernel and its taskman 0.30 0.36 lq QSOE/L — the seL4 taskman, its seam and its kernel patches 0.26 0.32 libc the C library, libqsoe and crt0 0.19 0.25 quser the shared userspace 0.18 0.24 qupkg the package manager, new in this release — 0.2 mr-bml the bootloader, shipped alongside 1.0 1.0 0.3 gave you a disk that keeps what you wrote. 0.4 gives you a system you can listen to, and one you install rather than unpack. QSOE now plays sound on every board it runs on, on both kernels, and plays it cleanly while the rest of the machine is busy. The base system is a package, a package manager adds to it, and a C compiler installed that way has built and run its first program on QSOE's own filesystem. Under all that, the two kernels moved closer together than ever: one boot archive boots both, the C library is one binary fo...