Overview of Vitruvian OS 0.3 on QEMU As we have posted earlier about the team behind Vitruvian OS announcing version 0.3 to the public for the first time, this project is not yet another Linux distribution. It's a Linux-based operating system with BeOS components on top, with the Nexus module to allow BeOS applications to run on top of Linux for maximum compatibility. If you have been our long time reader, you might have noticed that we've tested…

We ran VitruvianOS 0.3 on QEMU!

#Vitruvian #VitruvianOS #Linux #Kernel #LinuxKernel #Computers #Laptops #TechNews #TechUpdates #QEMU #BeOS #Haiku #HaikuOS

VitruvianOS ossia il ritorno di BeOS VitruvianOS reinterpreta la filosofia BeOS su base Linux con kernel real‑time, integrazioni Be‑like e un desktop coerente.

VitruvianOS riporta in vita l’idea di BeOS, ma su Linux: reattività, coerenza, kernel real‑time e un desktop progettato con una visione chiara. Un progetto che riapre domande importanti sul futuro del desktop. #VitruvianOS #Linux #BeOS

VitruvianOS 0.3 has been released as the project’s first publicly available version, described by its developers as a pilot build. It is based on the Linux kernel and adopts a design inspired by Haiku OS and BeOS. For reference, VitruvianOS’s development began in 2019, and now, in 2026, this version serves more as a functional foundation rather than a complete system. But before we go further, a few words about the project itself, since the name is probably unfamiliar to the general public. VitruvianOS is not a Linux distribution in the usual sense. It uses the Linux kernel only for hardware support, while replacing the standard Linux userland and desktop stack with its own components. Its goal is to combine Linux compatibility with a BeOS-style architecture. VitruvianOS 0.3 Let me explain. In a typical Linux desktop system, applications run on top of libraries and a display server such as X11 or Wayland. However, VitruvianOS removes this entire layer. It does not use X11 nor Wayland. Instead, it implements its own graphics system, input handling, and application runtime. A key feature is Nexus, an internal communication layer that manages messaging between system components. The system features native desktop elements modeled after BeOS, including a Deskbar and a Tracker-style file manager. It also offers a compatibility layer to support applications built for Haiku and BeOS APIs. Moreover, the system uses a Linux kernel with real-time patches. Regarding filesystems, VitruvianOS 0.3 supports XFS and SquashFS, as well as extended attributes. In the announcement, the developers have also outlined a short-term roadmap. Version 0.3.1 will add missing components and bug fixes based on initial testing. Version 0.3.2 aims to move the system toward self-hosting, enabling VitruvianOS to build itself. Next, the upcoming 0.4 release will focus on stability and broader hardware support, including ongoing ARM port development. Planned improvements also include enhanced input handling, a complete keymap system, and further user interface refinements. For more details, see the announcement. Finally, once again: keep in mind that VitruvianOS 0.3 is an experimental release intended mainly for testing and development. _Image credits: VitruvianOS_

@ActionRetro

Have you come across this?

VitruvianOS used the Linux Kernel but the uses it own window manager and is compatible with Haiku and BeOS apps 🙂

linuxiac.com/vitruvianos-0-3-debuts-a...

#Hauku #VitruvianOS

Vitruvian OS 0.3 has reached general availability! A project, which was in development since 2019 with very little appearance, has shown up this week, with a very interesting project that the team behind it is so excited to announce. This project is called Vitruvian OS, which combines the simplicity of BeOS (and Haiku) with the modernity of Linux to build an ultimate system intended to run BeOS applications under the Linux kernel!

Vitruvian OS 0.3 has reached general availability!

#Linux #BeOS #Vitruvian #VitruvianOS #Haiku #HaikuOS #Computers #Laptops #TechNews #TechUpdates #Kernel #LinuxKernel