<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VitruvianOS</title><link>https://v-os.dev/</link><description>Recent content on VitruvianOS</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 19 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://v-os.dev/index.xml" rel="self" type="application/rss+xml"/><item><title>ext4, OpenGL, and the new media2 kit</title><link>https://v-os.dev/blog/2026/07/19/ext4-opengl-and-the-new-media2-kit/</link><pubDate>Sun, 19 Jul 2026 00:00:00 +0000</pubDate><guid>https://v-os.dev/blog/2026/07/19/ext4-opengl-and-the-new-media2-kit/</guid><description>&lt;p&gt;Three things landed in the tree recently and they&amp;rsquo;re worth a short note.&lt;/p&gt;
&lt;h2 id="raw-images-now-ship-on-ext4"&gt;Raw images now ship on ext4&lt;/h2&gt;
&lt;p&gt;We used to build raw images on XFS. XFS handles xattrs well, and Vitruvian
uses xattrs everywhere for BFS-style metadata, so it felt right at the time.
The move to ext4 is more about what ext4 has become than about anything wrong
with XFS.&lt;/p&gt;
&lt;p&gt;Modern ext4 has &lt;code&gt;ea_inode&lt;/code&gt;, which lets a single attribute take up a whole
inode instead of the spare space in the file&amp;rsquo;s own inode. That means larger
attrs don&amp;rsquo;t spill and don&amp;rsquo;t fragment. Together with &lt;code&gt;large_dir&lt;/code&gt; and
&lt;code&gt;metadata_csum&lt;/code&gt;, ext4 covers our metadata needs.&lt;/p&gt;</description></item><item><title>VitruvianOS 0.5.0</title><link>https://v-os.dev/news/vitruvian-0.5.0/</link><pubDate>Sun, 19 Jul 2026 00:00:00 +0000</pubDate><guid>https://v-os.dev/news/vitruvian-0.5.0/</guid><description>&lt;p&gt;This is the login and media release. 0.4.1 got the filesystem talking to
Tracker. 0.5.0 gets the desktop talking to real users and starts wiring up
a real audio pipeline.&lt;/p&gt;
&lt;p&gt;Changelog&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Multi-user login. Janus now runs a pre-auth chain as a dedicated
&lt;code&gt;vos_login&lt;/code&gt; sysuser, launches the greeter, and after PAM authentication
respawns the graphical stack as the real user. Autologin is still
supported for CI images via a kernel cmdline flag.&lt;/li&gt;
&lt;li&gt;FirstBootPrompt on live media. Fresh live ISO boots straight into the
language picker and Try/Install screen.&lt;/li&gt;
&lt;li&gt;Sender-UID gate on &lt;code&gt;B_LAUNCH_JOB&lt;/code&gt;. The kernel plumbs the sender&amp;rsquo;s UID
into &lt;code&gt;BMessage&lt;/code&gt;, and janus refuses cross-user job launches.&lt;/li&gt;
&lt;li&gt;Locale and keymap picked in the greeter carry into the desktop, and for
the Installer into the installed target.&lt;/li&gt;
&lt;li&gt;Media2 kit merged. &lt;code&gt;BSoundPlayer&lt;/code&gt;, &lt;code&gt;BMediaFile&lt;/code&gt;, &lt;code&gt;BMediaTrack&lt;/code&gt;,
&lt;code&gt;BMediaRecorder&lt;/code&gt;, &lt;code&gt;BParameterWeb&lt;/code&gt; reimplemented on top of PipeWire and
GStreamer. Very early, it builds and links and the plumbing is in
place, but it isn&amp;rsquo;t stable yet. The &lt;code&gt;Sounds&lt;/code&gt; preferences preflet is
included with the same caveat.&lt;/li&gt;
&lt;li&gt;Game kit updated on top of media2 (BGameSound family).&lt;/li&gt;
&lt;li&gt;Storage kit gains &lt;code&gt;GetStatX&lt;/code&gt; for real creation-time via &lt;code&gt;statx(2)&lt;/code&gt;.
Legacy &lt;code&gt;GetStat&lt;/code&gt; still works.&lt;/li&gt;
&lt;li&gt;Ctrl+Alt+Del now opens the shutdown dance instead of hard-rebooting.
The registrar bridges systemd for logout / shutdown / reboot. Live ISOs
no longer hang for 90 seconds at power-off.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;getty@tty1&lt;/code&gt; masked on the graphical path so no pre-auth sysuser gets a
shell before the greeter. &lt;code&gt;getty@tty2&lt;/code&gt; stays as recovery.&lt;/li&gt;
&lt;li&gt;NodePreloader skips its warm-up on live media, cutting cold-boot time.&lt;/li&gt;
&lt;li&gt;Node monitor V-Race kernel bugs fixed (fanotify mark teardown UAF, vref
drop-after-unlock).&lt;/li&gt;
&lt;li&gt;App icon loading race in Deskbar fixed.&lt;/li&gt;
&lt;li&gt;DoCatalogs sweep, 80+ apps and preflets now install their translation
catalogs, so non-English UIs actually get translated.&lt;/li&gt;
&lt;li&gt;Installer text refreshed.&lt;/li&gt;
&lt;li&gt;First GPU back buffer path lit up on the DRM backend. Not on by default
yet, the cross-thread rendering context and the software fallback for
drivers that refuse hardware acceleration still need work.&lt;/li&gt;
&lt;li&gt;Cursor and dirty-region fixes, plus assorted small visual glitches.&lt;/li&gt;
&lt;li&gt;Improvements to &lt;code&gt;wait_for_thread&lt;/code&gt; semantics and the nexus kernel
module&amp;rsquo;s thread-exit path.&lt;/li&gt;
&lt;li&gt;As always, lots of small fixes.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="downloads"&gt;Downloads&lt;/h2&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Architecture&lt;/th&gt;
 &lt;th&gt;ISO&lt;/th&gt;
 &lt;th&gt;Raw&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;amd64&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;a href="https://github.com/VitruvianOS/Vitruvian/releases/download/0.5.0/Vitruvian-0.5.0-amd64.iso"&gt;Vitruvian-0.5.0-amd64.iso&lt;/a&gt;&lt;/td&gt;
 &lt;td&gt;&lt;a href="https://github.com/VitruvianOS/Vitruvian/releases/download/0.5.0/Vitruvian-0.5.0-amd64.raw"&gt;Vitruvian-0.5.0-amd64.raw&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;arm64&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;a href="https://github.com/VitruvianOS/Vitruvian/releases/download/0.5.0/Vitruvian-0.5.0-arm64.iso"&gt;Vitruvian-0.5.0-arm64.iso&lt;/a&gt;&lt;/td&gt;
 &lt;td&gt;&lt;a href="https://github.com/VitruvianOS/Vitruvian/releases/download/0.5.0/Vitruvian-0.5.0-arm64.raw"&gt;Vitruvian-0.5.0-arm64.raw&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&lt;a href="https://github.com/VitruvianOS/Vitruvian/releases/tag/0.5.0"&gt;GitHub release page&lt;/a&gt;&lt;/p&gt;</description></item><item><title>VitruvianOS 0.4.1</title><link>https://v-os.dev/news/vitruvian-0.4.1/</link><pubDate>Fri, 26 Jun 2026 00:00:00 +0000</pubDate><guid>https://v-os.dev/news/vitruvian-0.4.1/</guid><description>&lt;p&gt;This is the filesystem release. However, from this point on the majority of the system nervous system is now connected and Tracker is receiveing filesystem notifications. For the time being we suggest not using this release outside vm or on a computer where you have a partition you care about.&lt;/p&gt;
&lt;p&gt;Changelog&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed various filesystem and Tracker related issues. Now Tracker can be effectively used to manipulate directories and files.&lt;/li&gt;
&lt;li&gt;Node monitor surgery to get it able to sustain realistic workloads.&lt;/li&gt;
&lt;li&gt;File opening through apps now works.&lt;/li&gt;
&lt;li&gt;General improved stability of Tracker and Deskbar fs-related menus.&lt;/li&gt;
&lt;li&gt;All problems with apps being stuck in Deskbar on quit are fixed.&lt;/li&gt;
&lt;li&gt;Enabled Tracker Add-Ons and Templates.&lt;/li&gt;
&lt;li&gt;Implemented userland and kernel level mechanisms to ensure virtual references interoperability for inter app communication.&lt;/li&gt;
&lt;li&gt;Add GLTeapot using mesa surfaceless backend, still buggy but will run and you can drag it.&lt;/li&gt;
&lt;li&gt;Fixed Tracker in navigation mode (going to be default next release).&lt;/li&gt;
&lt;li&gt;Lots of performance improvements visible.&lt;/li&gt;
&lt;li&gt;Implemented XDG Trash.&lt;/li&gt;
&lt;li&gt;Improved startup and shutdown speed including janus improvements.&lt;/li&gt;
&lt;li&gt;Memory usage improvements and memory leak fixes.&lt;/li&gt;
&lt;li&gt;Fixed a problem with app_server and racy area resizing that couldn&amp;rsquo;t possibly work on Linux (fixes BBitmap crashes completely).&lt;/li&gt;
&lt;li&gt;Added prototype caps-based ports for secure file handle passing.&lt;/li&gt;
&lt;li&gt;Screen can now change resolution.&lt;/li&gt;
&lt;li&gt;Improved app_server drawing performance.&lt;/li&gt;
&lt;li&gt;Switch default raw images filesystem to EXT4 (see upcoming development article in v-os.dev)&lt;/li&gt;
&lt;li&gt;Introduced initial support for building makefile based apps inside vitruvian.&lt;/li&gt;
&lt;li&gt;As always lots of little fixes impossible to enumerate.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Be patient.&lt;/p&gt;</description></item><item><title>Introducing the Janus Privileged Launcher</title><link>https://v-os.dev/blog/2026/06/02/introducing-the-janus-privileged-launcher/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://v-os.dev/blog/2026/06/02/introducing-the-janus-privileged-launcher/</guid><description>&lt;p&gt;You know how on a normal Linux desktop you need a display manager to log in, and then a bunch of services start in the background, Vitruvian works differently but not too much. It uses a privileged launcher called janus that does all of that and more.&lt;/p&gt;
&lt;p&gt;Its job is to bring up the entire Vitruvian desktop and keep it running until shutdown. It replaces a display manager, it replaces a traditional init style service launcher, and it does a bunch of low level hardware coordination that neither of those normally handles.&lt;/p&gt;</description></item><item><title>VitruvianOS 0.4.0</title><link>https://v-os.dev/news/vitruvian-0.4.0/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://v-os.dev/news/vitruvian-0.4.0/</guid><description>&lt;p&gt;A broad foundation release: better hardware support, a saner desktop session, and a more reliable build pipeline.&lt;/p&gt;
&lt;h2 id="whats-new-from-032"&gt;What&amp;rsquo;s new from 0.3.2&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Desktop session manager (janus)&lt;/strong&gt;. Vitruvian now starts, manages, and shuts down its servers through a proper session manager instead of ad-hoc scripts. Logins and reboots are cleaner and more predictable.&lt;/p&gt;
&lt;h3 id="display-and-input"&gt;Display and input&lt;/h3&gt;
&lt;p&gt;The graphics backend works on more GPUs and handles multi-seat hardware transitions cleanly. Keyboard input now uses the native Linux keymap system, so non-US layouts and special keys start to behave the way you&amp;rsquo;d expect.&lt;/p&gt;</description></item><item><title>VitruvianOS 0.3.2</title><link>https://v-os.dev/news/vitruvian-0.3.2/</link><pubDate>Sat, 04 Apr 2026 00:00:00 +0000</pubDate><guid>https://v-os.dev/news/vitruvian-0.3.2/</guid><description>&lt;p&gt;We are pleased to announce the release of Vitruvian OS 0.3.2.
This is a bit of an anticipated release in preparation of big changes for the next.&lt;/p&gt;
&lt;p&gt;We would like to thank everyone again for the encouraging amount of support!&lt;/p&gt;
&lt;p&gt;What you will find in the new ISO:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Stability fixes&lt;/li&gt;
&lt;li&gt;Pulse, DiskProbe, ActivityMonitor and other apps are beginning to work.&lt;/li&gt;
&lt;li&gt;Devices enumeration (fs features start appearing)&lt;/li&gt;
&lt;li&gt;Lots of minor fixes&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You can download the iso at the following link:&lt;/p&gt;</description></item><item><title>VitruvianOS 0.3.1</title><link>https://v-os.dev/news/vitruvian-0.3.1/</link><pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate><guid>https://v-os.dev/news/vitruvian-0.3.1/</guid><description>&lt;p&gt;As promised we are pleased to announce the release of Vitruvian OS 0.3.1.&lt;/p&gt;
&lt;p&gt;We would like to thank everyone for the encouraging amount of support for
the first public release of Vitruvian.&lt;/p&gt;
&lt;p&gt;What you will find in the new ISO:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Resolved most problems with icons.&lt;/li&gt;
&lt;li&gt;Lots of new apps and preferences&lt;/li&gt;
&lt;li&gt;Double buffering in app_server&lt;/li&gt;
&lt;li&gt;Fixed BIOS Machines Boot&lt;/li&gt;
&lt;li&gt;Improved general stability&lt;/li&gt;
&lt;li&gt;Tracker fixes&lt;/li&gt;
&lt;li&gt;Kernel fixes&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;What happened during development (that we still didn&amp;rsquo;t release):&lt;/p&gt;</description></item><item><title>Support Vitruvian on DistroWatch</title><link>https://v-os.dev/news/support-us-on-distrowatch/</link><pubDate>Thu, 26 Mar 2026 00:00:00 +0000</pubDate><guid>https://v-os.dev/news/support-us-on-distrowatch/</guid><description>&lt;p&gt;If you like Vitruvian, you can help it out in just a few seconds.&lt;/p&gt;
&lt;p&gt;Go to &lt;a href="https://distrowatch.com/dwres.php?resource=links#new"&gt;DistroWatch&lt;/a&gt;, find Vitruvian in the list, and click &amp;ldquo;Recommend&amp;rdquo; next to it.
That&amp;rsquo;s all, no login needed.&lt;/p&gt;
&lt;p&gt;Thank you!&lt;/p&gt;</description></item><item><title>VitruvianOS: Interview with the team</title><link>https://v-os.dev/news/interview-with-vitruvian-team/</link><pubDate>Wed, 25 Mar 2026 00:00:00 +0000</pubDate><guid>https://v-os.dev/news/interview-with-vitruvian-team/</guid><description>&lt;h2 id="interview-with-the-vitruvian-os-founder"&gt;Interview with the Vitruvian OS founder&lt;/h2&gt;
&lt;p&gt;Following our release announcement (link below), we&amp;rsquo;re happy to share an
interview with the Vitruvian founder about the project future and philosophy:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.desktoponfire.com/interview/846/an-interview-with-dario-casalinuovo-from-beos-to-vitruvianos/"&gt;An interview with Dario Casalinuovo — From BeOS to VitruvianOS&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Download VitruvianOS 0.3.0&lt;/strong&gt;: &lt;a href="https://v-os.dev/download/"&gt;v-os.dev&lt;/a&gt;
&lt;strong&gt;VitruvianOS 0.3.0 Announcement&lt;/strong&gt;: &lt;a href="https://v-os.dev/news/vitruvian-0.3.0-available/"&gt;0.3.0&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Join the community&lt;/strong&gt;: &lt;a href="https://t.me/vitruvian_official_chat"&gt;Telegram&lt;/a&gt; | &lt;a href="https://github.com/VitruvianOS/Vitruvian"&gt;GitHub&lt;/a&gt;&lt;/p&gt;</description></item><item><title>VitruvianOS 0.3.0</title><link>https://v-os.dev/news/vitruvian-0.3.0-available/</link><pubDate>Mon, 23 Mar 2026 00:00:00 +0000</pubDate><guid>https://v-os.dev/news/vitruvian-0.3.0-available/</guid><description>&lt;p&gt;&lt;strong&gt;VitruvianOS&lt;/strong&gt; — is an operating system built on Linux that is inspired by the BeOS. After years of quiet development, we&amp;rsquo;re thrilled to announce the first public release of VitruvianOS 0.3.0.&lt;/p&gt;
&lt;p&gt;This is a milestone moment—not just for us.&lt;/p&gt;
&lt;h2 id="why-now"&gt;Why Now?&lt;/h2&gt;
&lt;p&gt;We started the first experiments in 2019, but the first announcement was more of a quiet signal to the few people who might care.&lt;/p&gt;
&lt;p&gt;Porting a BeOS-compatible runtime on top of Linux isn&amp;rsquo;t like repackaging existing tools. We built the entire infrastructure from scratch—a sophisticated layer that allows the Tracker, Deskbar, and the rest of the Vitruvian experience to run as fully native Linux applications.&lt;/p&gt;</description></item><item><title>Building a Haiku Runtime on Linux: The Road So Far</title><link>https://v-os.dev/blog/2026/02/10/building-a-haiku-runtime-on-linux-the-road-so-far/</link><pubDate>Tue, 10 Feb 2026 00:00:00 +0000</pubDate><guid>https://v-os.dev/blog/2026/02/10/building-a-haiku-runtime-on-linux-the-road-so-far/</guid><description>&lt;p&gt;One of the core challenges in building V\OS is bridging two worlds: the Linux kernel&amp;rsquo;s POSIX model and the BeOS/Haiku API&amp;rsquo;s distinct approach to system services (messaging, node monitoring, virtual filesystems, and more). This post gives a brief look at how we are approaching it.&lt;/p&gt;
&lt;h2 id="the-kernel-bridge"&gt;The Kernel Bridge&lt;/h2&gt;
&lt;p&gt;Rather than running a BeOS kernel, Vitruvian implements the missing pieces as Linux kernel modules. The &lt;code&gt;nexus&lt;/code&gt; module brings BeOS-style node monitoring to Linux&amp;rsquo;s &lt;code&gt;fsnotify&lt;/code&gt; subsystem, translating filesystem events into the &lt;code&gt;B_NODE_MONITOR&lt;/code&gt; messages that BeOS/Haiku applications expect. This allows Tracker, the file manager, to watch directories and respond to changes in real time, exactly as it would on native Haiku.&lt;/p&gt;</description></item><item><title>Vitruvian OS: Project (Re)Announcement</title><link>https://v-os.dev/news/project-reannounced/</link><pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate><guid>https://v-os.dev/news/project-reannounced/</guid><description>&lt;p&gt;&lt;strong&gt;Vitruvian&lt;/strong&gt;: an operating system built on Linux that brings the elegance and simplicity of BeOS to modern hardware.&lt;/p&gt;
&lt;p&gt;Vitruvian is in active development. Daily builds will be soon available for early adopters who want to follow progress.
The system boots on modern x86-64 hardware, runs a Linux kernel, and includes a working BeOS/Haiku API compatibility layer.&lt;/p&gt;</description></item><item><title>About Vitruvian</title><link>https://v-os.dev/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v-os.dev/about/</guid><description>&lt;h2 id="what-is-vitruvianos"&gt;What is VitruvianOS?&lt;/h2&gt;
&lt;p&gt;Vitruvian, also known as &lt;strong&gt;V\OS&lt;/strong&gt;, is the human-centric Operating System. Built on Linux and inspired by BeOS, it brings the elegance and simplicity of a classic operating system to modern hardware without sacrificing the power and hardware support that Linux provides.&lt;/p&gt;
&lt;p&gt;Custom-built kernel modules deliver a responsive, low-latency desktop experience. The BeOS/Haiku API is supported on Linux with minimal to no changes required to application source code.&lt;/p&gt;</description></item><item><title>Contact</title><link>https://v-os.dev/contact/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v-os.dev/contact/</guid><description>&lt;h2 id="get-in-touch"&gt;Get in Touch&lt;/h2&gt;
&lt;p&gt;The best way to reach the Vitruvian team is through our community channels.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;GitHub Issues&lt;/strong&gt;: &lt;a href="https://github.com/VitruvianOS/Vitruvian/issues"&gt;github.com/VitruvianOS/Vitruvian/issues&lt;/a&gt;: bug reports, feature requests, questions&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Telegram Chat&lt;/strong&gt;: &lt;a href="https://t.me/vitruvian_official_chat"&gt;t.me/vitruvian_official_chat&lt;/a&gt;: general discussion and support&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Telegram Updates&lt;/strong&gt;: &lt;a href="https://t.me/vitruvian_official"&gt;t.me/vitruvian_official&lt;/a&gt;: announcements and project news&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mailing List&lt;/strong&gt;: &lt;a href="https://www.freelists.org/list/vitruvian"&gt;freelists.org/list/vitruvian&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Donate</title><link>https://v-os.dev/donate/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v-os.dev/donate/</guid><description>&lt;h2 id="donate"&gt;Donate&lt;/h2&gt;
&lt;p&gt;Vitruvian is developed by volunteers in their spare time. If you find the project useful and want to support its development, donations are welcome.&lt;/p&gt;
&lt;p&gt;Even a small donation such as the price of a coffee in your country can change the world. Donations are not only about financial stability but also helpful to charge developer&amp;rsquo;s motivation that can be lacking at times.&lt;/p&gt;
&lt;p&gt;Support VitruvianOS through one of the following platforms:&lt;/p&gt;</description></item><item><title>Download</title><link>https://v-os.dev/download/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v-os.dev/download/</guid><description>&lt;h2 id="download-vitruvianos"&gt;Download VitruvianOS&lt;/h2&gt;
&lt;h3 id="latest-release"&gt;Latest Release&lt;/h3&gt;
&lt;p&gt;The current release is always available from GitHub:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/VitruvianOS/Vitruvian/releases/latest"&gt;Download latest release&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Release notes for each version are on the &lt;a href="https://v-os.dev/releases/"&gt;Releases&lt;/a&gt; page.&lt;/p&gt;
&lt;h3 id="build-from-source"&gt;Build from Source&lt;/h3&gt;
&lt;p&gt;To build the system from source, follow the instructions in the wiki:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://wiki.v-os.dev/docs/getting-started/building/"&gt;Build Instructions&lt;/a&gt;&lt;/p&gt;
&lt;h3 id="install"&gt;Install&lt;/h3&gt;
&lt;p&gt;See the &lt;a href="https://wiki.v-os.dev/docs/getting-started/how-to-install/"&gt;How To Install&lt;/a&gt; guide for writing images to USB drives and first boot instructions.&lt;/p&gt;
&lt;h3 id="system-requirements"&gt;System Requirements&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;x86-64 or arm64 processor (RISC-V in progress)&lt;/li&gt;
&lt;li&gt;512 MB RAM minimum (4 GB recommended)&lt;/li&gt;
&lt;li&gt;1 GB disk space&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="getting-help"&gt;Getting Help&lt;/h3&gt;
&lt;p&gt;If something breaks, open a ticket on &lt;a href="https://github.com/VitruvianOS/Vitruvian/issues"&gt;GitHub Issues&lt;/a&gt; or ask in the &lt;a href="https://t.me/vitruvian_official_chat"&gt;Telegram chat&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>FAQ</title><link>https://v-os.dev/faq/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v-os.dev/faq/</guid><description>&lt;h2 id="what-is-vitruvianos"&gt;What is VitruvianOS?&lt;/h2&gt;
&lt;p&gt;Vitruvian is an operating system based on Linux, inspired by the BeOS. It brings the BeOS/Haiku API and desktop philosophy to modern hardware, running on a Linux kernel with custom kernel modules.&lt;/p&gt;
&lt;h2 id="is-it-based-on-haiku"&gt;Is it based on Haiku?&lt;/h2&gt;
&lt;p&gt;Partially. Vitruvian uses the Linux kernel and implements the BeOS/Haiku API compatibility layer on top of it. It is inspired by both BeOS and Haiku but is an independent project built from the ground up where we picked the best available open source components.&lt;/p&gt;</description></item><item><title>Screenshots</title><link>https://v-os.dev/screenshots/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v-os.dev/screenshots/</guid><description/></item></channel></rss>