⏱️ Lectura: 9 min
Haiku, the operating system that rebuilds the BeOS experience from scratch, released version R1/beta6 on August 26, 2026: nearly two years after beta5 and just a week after the project turned 25. The release is already available to download from haiku-os.org, with an “anyboot” image ready to install on real hardware or run in a virtual machine.
📑 En este artículo
This milestone matters because Haiku is one of the few active operating systems that isn’t derived from Linux, BSD, or Windows: it maintains its own kernel, its own graphical interface, and its own family of C++ APIs, direct heirs of BeOS, the system Be Inc. launched in 1996 to compete against Mac OS and Windows 95.
TL;DR
- Haiku R1/beta6 was released on August 26, 2026, according to the official announcement on haiku-os.org.
- It arrived nearly two years after beta5 and just a week after the project’s 25th anniversary.
- It’s downloaded as an anyboot image: it works both for burning to a USB drive and for mounting in a VM.
- Haiku rebuilds BeOS’s architecture and APIs from scratch, the system Be Inc. released in 1996.
- The system uses its own C++ kernel, its BFS file system, and its packagefs package manager.
- HaikuDepot works as a native app store, with .hpkg packages that can be activated without installation scripts.
- The final R1 release (without “beta”) still has no confirmed date after six betas since 2018.
What Happened
The Haiku team confirmed the release of Haiku R1/beta6 on its official blog, along with release notes and press contacts for media outlets wanting to cover the news. The announcement comes at a symbolic moment: the project was born in 2001, and beta6 was published just seven days after its 25th anniversary.
Unlike an annual release cycle like the one used by the best-known Linux distributions, Haiku moves forward with betas spaced years apart. This is the sixth since the project dropped numbered alphas and adopted the “beta” scheme to move closer to a formal 1.0 release. The team didn’t publish an exhaustive changelog in the announcement, but pointed to the release notes section on the official site for the full details of the changes.
Context and History
To understand why Haiku exists, you have to go back to 2001. Be Inc., the company founded by former Apple executive Jean-Louis Gassée, had built BeOS as a multimedia operating system designed for BeBox workstations, with a focus on performance, native multithreading, and a clean interface. When Palm bought Be Inc.’s assets in 2001 and discontinued BeOS, a group of users and developers launched OpenBeOS: an attempt to reimplement the system from scratch, without access to the original source code.
The project was renamed Haiku in 2004 due to trademark conflicts with Palm, which held the rights to the name “BeOS”. Since then, Haiku Inc. (the nonprofit organization behind the project) has coordinated years of development that produced alphas 1 through 4 between 2009 and 2012, followed by a series of betas that began in 2018. Beta6 continues that slow but steady pace, typical of an operating system maintained almost entirely by volunteers.
Architecture and Technical Details
What sets Haiku apart from most modern operating systems is that it doesn’t reuse an existing kernel. Its core, derived from the NewOS project, is written in C++ and exposes its own driver model, with no binary compatibility layer for Linux modules. Running on top of the kernel is a set of libraries called “kits”: the Interface Kit draws windows and widgets, the Application Kit manages process lifecycle and messaging between apps, and the Media Kit handles audio and video with the same low-level philosophy BeOS had in the 1990s.
The native file system is BFS (Be File System), designed from the start with indexed extended attributes: it allows queries like “find all MP3s longer than 4 minutes” directly against filesystem metadata, without scanning file by file. Software management runs on packagefs, which mounts each .hpkg package as a read-only layer and activates or deactivates full system versions without traditional installation scripts, which greatly simplifies rollback in case of a problematic update.
flowchart TD
A["Native applications (Be API)"] --> B["Application Kit"]
A --> C["Interface Kit"]
A --> D["Media Kit"]
B --> E["Haiku Kernel"]
C --> E
D --> E
E --> F[("packagefs / BFS")]
E --> G["Native drivers"]💭 Key point: unlike apt or dpkg, packagefs doesn’t run scripts on install: it simply activates or deactivates .hpkg files as mounted layers, which makes reverting an update instantaneous.
How to Try It Today
The fastest way to get to know Haiku R1/beta6 without touching a real partition is to run it in a virtual machine. With QEMU installed, it’s enough to download the anyboot image from haiku-os.org and boot it directly:
qemu-system-x86_64 \
-m 2048 \
-smp 2 \
-cdrom haiku-r1beta6-x86_64-anyboot.iso \
-boot dThat command boots Haiku with 2 GB of RAM and two virtual cores, booting directly from the ISO image. It’s enough to explore the Deskbar, HaikuDepot, and WebPositive without installing anything on the physical disk.
To install on real hardware, you need to burn the same anyboot image to a USB drive, and the procedure changes depending on the operating system you’re preparing it from:
# Linux: identify the device with lsblk and then burn it
lsblk
sudo dd if=haiku-r1beta6-x86_64-anyboot.iso of=/dev/sdX bs=4M status=progress conv=fsync
# macOS: locate the disk with diskutil and burn in raw mode
diskutil list
sudo dd if=haiku-r1beta6-x86_64-anyboot.iso of=/dev/rdiskN bs=4mOn Windows there’s no direct equivalent to dd in the standard terminal, so the recommended route is a graphical tool like Rufus or balenaEtcher: select the anyboot image as the source, the USB as the destination, and burn it in “DD image” mode (not ISO mode), so the USB ends up bootable just like on Linux or macOS.
Once inside Haiku, you can confirm the exact version installed by opening the Deskbar menu and going into “About This Haiku”, or by running uname -a in the Terminal, which should report the beta6 revision used to build the image.
Impact and Analysis
Haiku competes in a very particular niche: operating systems that aren’t forks of something bigger. Here’s how it compares to other projects that also rebuild systems from scratch or reimplement someone else’s APIs:
| Project | Approach | Status in 2026 | Compatibility with existing apps |
|---|---|---|---|
| Haiku | Rebuild of BeOS, own C++ kernel and kits | R1/beta6, active development | Native Be API apps; limited POSIX layer |
| SerenityOS | Tribute to 90s aesthetics, written from scratch | No numbered releases, continuous development | Own ecosystem, no external compatibility |
| ReactOS | Reimplementation of the Windows NT API | Permanent alpha/beta for over two decades | High compatibility with Windows XP/2003 binaries |
| FreeDOS | Free reimplementation of MS-DOS | Stable, ongoing maintenance | High compatibility with 80s and 90s DOS software |
Haiku’s advantage over those projects is that it actually reaches numbered betas with a public timeline, and its API remains source-compatible with original 1990s BeOS applications in many cases, something uncommon in a system that also runs on modern x86_64 hardware.
⚠️ Watch out: hardware support remains the weak point. Wifi, recent GPUs, and modern laptops usually depend on drivers written and maintained by volunteers, so testing it first in a VM avoids surprises when installing on a current laptop.
That’s precisely Haiku’s central trade-off: it gains design coherence and package model simplicity, but pays the cost of not being able to rely on the driver work that Linux and the BSDs share with each other.
What’s Next
The beta6 announcement didn’t include a date for the final R1 release, which would drop the “beta” label after six rounds since 2018. The project’s historical pattern (years between each beta, development sustained by a small community) suggests the focus of upcoming iterations will remain stability, more hardware support via HaikuPorts, and incremental improvements to WebPositive, the native WebKit-based browser.
📖 Summary on Telegram: View summary
Try it yourself: download the Haiku R1/beta6 anyboot image from haiku-os.org and boot it today in QEMU using the command from this article.
Frequently Asked Questions
What is Haiku OS?
It’s an open-source operating system that rebuilds BeOS’s architecture and APIs from scratch, the system Be Inc. launched in 1996. It’s not based on the Linux kernel or any BSD.
How is it different from the original BeOS?
Haiku doesn’t use BeOS source code: it was rewritten starting in 2001 by volunteers after Palm’s acquisition of Be Inc., keeping the same API philosophy and interface design.
Can I run Windows or Linux apps on Haiku?
Not natively. Haiku runs software written against its own C++ Be API; there’s a limited POSIX compatibility layer for command-line tools, but no binary emulator for Windows or Linux.
What hardware does Haiku R1/beta6 support?
It runs mainly on x86_64 architecture, with driver support maintained by the community. Wifi and recent GPU support is limited compared to Linux, so testing it in a virtual machine is the safest route before installing it on real hardware.
Is it free and open source?
Yes. Haiku’s code is publicly available, and the project is sustained through Haiku Inc., a nonprofit organization funded by community donations.
When will the final R1 release come out?
The beta6 announcement didn’t specify a date. The project has gone through six betas since 2018 without setting a public timeline for the definitive 1.0 release.
References
- Official Haiku R1/beta6 announcement: original post on the haiku-os.org news blog.
- Haiku OS, official site: downloads, documentation, and release notes for the project.
- Haiku repository on GitHub: mirror of the source code for the kernel, the kits, and the native applications.
- Haiku (operating system), Wikipedia: the project’s history from its origins as OpenBeOS in 2001.
📱 Do you like this content? Follow @programacion on Telegram for daily tech content in Spanish: quick summaries, fresh content every day.
Imagen destacada: Foto de Alexander Grigoryev en Unsplash
0 Comments