Docs

FAQ

What is Vitruvian?

V is a Linux-based operating system inspired by BeOS. It runs the BeOS/Haiku desktop and API on a Linux kernel, with custom kernel modules (collectively called Nexus) filling in the BeOS system services that Linux doesn’t provide natively.

See the Nexus reference page for details.

Is it ready to use?

Nearly. The project is approaching beta. Most of the system works, including the desktop, multiuser login, the installer and DriveSetup, and BeOS/Haiku application source code compiles and runs with minimal changes. Work now centres on porting applications. Some rough edges remain.

What’s coming next?

How is it different from Haiku?

Haiku is a from-scratch reimplementation of BeOS with its own kernel. V runs on the Linux kernel instead, so it picks up Linux’s hardware support, driver ecosystem, and security model for free. The aim is to get close to full userland BeOS/Haiku API compatibility on top of that, without writing a kernel from scratch. Over time V will grow its own flavour and its own APIs.

How mature is the API compatibility?

The core kits (Application, Interface, Storage, Support) work well enough to run real BeOS/Haiku applications with little or no source changes. Some kits are further along than others.

Is there a package manager?

Yes, apt. The PackageManager application is a graphical front end to it, and the command line works as well.

Does Vitruvian run on this kernel or this platform?

V is based on a standard Linux kernel with the addition of the Nexus DKMS modules. Any not-too-ancient kernel should be able to run Vitruvian.

Is it binary compatible with BeOS or Haiku?

No. That would need a WINE-like layer, such as a runtime_loader port. Source-level compatibility is strong, though, and should cover most use cases.

Will I be able to run this program or that other program on Vitruvian?

V can run BeOS/Haiku and CLI applications for now. Command line programs such as Node.js, binutils or parted run as on any Linux system. GTK and Qt ports are available but have not been integrated in the system yet.

Is Vitruvian running on Xorg or Wayland?

V uses its own display server. The stack derives from the Haiku OS source code, although heavily modified to interface with modern Linux display and hardware accelerated APIs.

What filesystems are supported for booting?

ext4 by default, with XFS and Btrfs as alternatives and SquashFS on live images. See Filesystem Layout.

Will it run in a virtual machine?

Yes. QEMU with KVM is the recommended setup for testing. See Virtualization for guides.

What architectures are supported?

How do I get a copy?

Releases are on the download site. You can also build from source.

Is Vitruvian free?

Yes. It is released under a hybrid GPL/MIT license and is free of cost.

Can I contribute without being a kernel developer?

Yes. There’s useful work at every level: porting BeOS/Haiku applications, fixing desktop bugs, writing docs, testing on real hardware, filing issues, helping with the website. Come say hello on Telegram and ask where help is needed.

What is Nexus?

Nexus is a set of Linux kernel modules that bridge the Linux kernel with the BeOS/Haiku runtime. It implements ports, semaphores, shared memory areas, thread control, virtual references, and node monitoring, all the kernel APIs that Haiku provides natively but Linux doesn’t. See the Nexus page.

How do I report a bug?

Open an issue on GitHub. Include relevant log output, what you were doing, and what you expected to happen.

Can I donate?

Yes, see the Donate page.

Can I send hardware to the developers?

Hardware donations for testing and development are welcome. Reach out on Telegram to coordinate.

Where can I get help?

V\OS Docs