QSOE: QNX-inspired OS with dual-kernel architecture

Hacker News Top Products

Summary

QSOE project v0.1 is released, providing a QNX-compatible operating system with two microkernel variants (custom Skimmer kernel and seL4-based), shared userspace, and support for SiFive Unmatched RISC-V hardware.

No content available
Original Article
View Cached Full Text

Cached at: 06/24/26, 01:47 AM

# QSOE project v0.1 released Source: [https://qsoe-dev.blogspot.com/2026/06/qsoe-project-v01-is-released.html](https://qsoe-dev.blogspot.com/2026/06/qsoe-project-v01-is-released.html) ### QSOE project v0\.1 released The first QSOE release, v0\.1, is out\. It bundles both kernel variants, the boot loader, the userspace, and libc into a single numbered drop, and consists of the following components: - **QSOE/N v0\.17**, with the custom "Skimmer" kernel\. - **QSOE/L v0\.14**, which works together with seL4 version 15\. - **mr\-bml v0\.5\.1**, a GRUB\-derived boot loader with support for Multiboot 3, RISC\-V Linux\-style kernels, and kernels with an EFI stub\. - **quser v0\.5**, offering an mksh\-based shell \(qsh\)\. - **libc v0\.6**\. The two variants share the same userspace above the seam: quser, qsh, and libc are identical, with only taskman and libc\.so differing per kernel\. That shared userspace is the whole point — one QNX\-compatible environment over two very different microkernels\. The milestone behind this release is on the QSOE/L side: it now boots from NVMe storage to an interactive login shell on the SiFive Unmatched \(FU740\)\. Spawning the first program off a mounted disk had exposed a pair of deadlocks — taskman blocked reading the spawn image while the read chain's wakes routed back through it — so the`Sync\*`slow path and device\-interrupt pulses are now kernel\-direct, taking taskman out of the wake path entirely\. With QSOE/N \(v0\.17\) already spawning from its own filesystem to an interactive qsh, both variants now reach a shell on the FU740\. The source is on GitLab under Apache\-2\.0, at[gitlab\.com/qsoe](https://gitlab.com/qsoe)\. Binaries and documentation are hosted on GitHub, and download and installation instructions live on the project website,[qsoe\.net](https://qsoe.net/)\. ### Popular posts from this blog ### [How QSOE started](https://qsoe-dev.blogspot.com/2026/05/how-qsoe-started.html) It was the first of April, and work on QRV — my port of QNX to RISC\-V — was in full swing\. A couple of weeks earlier I had put up an open petition asking QNX Software Systems and BlackBerry to re\-license the historical 2007–2009 QNX Neutrino source under Apache 2\.0\. Around this time a thought settled in: there's a real chance it gets ignored completely\. I needed a plan B\. I've kept the L4 microkernel in the back of my mind for a long time\. I first read about it in the early 2000s, along with its various implementations — the ones with the nutty names \(Hazelnut, Pistachio\), and the one with the funny name, Fiasco, from the group in Dresden\. I met those people in person about ten years ago\. I never really stopped thinking about L4 after that; I knew about L4Linux and the rest\. And I got particularly interested when I learned about seL4\. What seL4's authors did still strikes me as a genuinely novel approach: a real microkernel with a machine\-checked proof of functional corr\.\.\. ### [A free QNX\-like operating system \(2003\)](https://qsoe-dev.blogspot.com/2026/06/a-free-qnx-like-operating-system-2003.html) I came across an old post of mine on the comp\.os\.qnx newsgroup, dated August 7, 2003\. The subject line was "A free QNX\-like operating system," and under it I announced RadiOS — a hobby effort to build a free, QNX\-compatible microkernel OS for x86, with the microkernel and task manager written entirely in NASM assembly\. About 70% of the required system calls were in place by then, along with parts of libc, a console resource manager, and an ATA/IDE driver; there was no filesystem manager yet\. The post asked whether anyone wanted to help hack on it, and signed off with "73\!"\. The thread is here: https://groups\.google\.com/g/comp\.os\.qnx/c/srdvVoik37M The fuller picture survives on the old SourceForge page, still up at radios\.sf\.net \. RadiOS targeted system\-call compatibility with QNX Neutrino 6\.1; its Task Manager mirrored the QNX process\-manager message format, and its libc was derived from QNX 6\.1 code\. By mid\-2004 it ran to roughly 45,000 lines, almost all NASM, w\.\.\.

Similar Articles

One man, two kernels, and a lot of RISC-V

Hacker News Top

Yuri Zaporozhets of QRV Systems has built a RISC-V-based personal computer and a mainframe on an FPGA, and rewritten QNX twice. His latest OS QSOE is gaining attention in the FOSS world.

QBE – Compiler Back End

Hacker News Top

QBE is a compact, hobby-scale compiler backend that provides 70% of the performance of industrial optimizing compilers in 10% of the code, supporting amd64, arm64, and riscv64 with a simple SSA-based intermediate language.

@no_stp_on_snek: https://x.com/no_stp_on_snek/status/2052833502475833384

X AI KOLs Following

An open-source stack using Qwen2.5-32B-Instruct with longctx and vllm-turboquant on a single AMD MI300X achieves competitive results (0.601-0.688) versus SubQ's closed model (0.659) on the MRCR v2 1M-context benchmark, demonstrating open-weights approaches are within striking distance.