Greg Kurtzer shifts Ginux from standalone kernel to userspace Linux compatibility layer
Greg Kurtzer's Ginux project, which began as a Rust-based kernel booting via UEFI with a Rocky Linux 10 userspace, has ended that experimental phase; its final code is preserved on a bootable-kernel branch and tag. Development now continues on a new version of Ginux that runs as an ordinary userspace process on top of Linux, mediating syscalls for isolated workloads rather than replacing the kernel.
GoKawiil's interpretation of the reporting above, not reported fact.
By running as a userspace process instead of competing with Linux's kernel ABI, Ginux could offer a narrower, versioned interface that lets operators restrict what isolated workloads can do, which may appeal to security- or compliance-focused environments. The shift suggests Kurtzer's team concluded that reproducing Linux's broader ecosystem of compatibility and community support wasn't a realistic goal for a from-scratch kernel, positioning Ginux instead as a controlled compatibility and sandboxing layer.
- Ginux has moved from an independent Rust kernel to a userspace kernel running atop Linux.
- The original bootable-kernel code is archived on a dedicated branch and tag for reference.
- Ginux now mediates syscalls to give isolated instances a deliberately smaller, versioned contract than full Linux ABI compatibility.
Source: github.com, 2026-11-11
Published there as: “Greg Kurtzer's Ginux is now a userspace kernel”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.