Haiku Archive
You know the drill by now – a new month, a new Haiku activity report. This past month doesn’t seem to have any big ticket items, but instead contains a long list of smaller but still welcome fixes. Various filesystem drivers saw some work, a few bugs in virtio drivers were fixed, and NVMM execution is now easily interruptible by signals which should improve performance in various emulators like QEMU. Be sure to comb through the complete list to see if there’s anything in there that impacts you.
Late 2000. There is a grey and blue tower PC on my dorm-room desk like nothing anybody who walks into the room has ever seen. The Be logo on the front, a 3.5″ floppy peeking out the bottom of the drive bays, and the vertical grille that hides two columns of green LEDs (blinkenlights) dancing with the CPU load. This was a dual-PowerPC workstation running an operating system you didn’t see in the wild. I was studying computer science at the time and this was a fun piece of hardware. ↫ J.D. Hodges As a BeOS user in and around 2001 or so, the BeBox was the holy grail of the little community I was a part of. There were some people here and there in online circles who had one, but they were rare even when new, and by 2001, they had become rarer still. This rarity made them mysterious and exciting from almost from the day they were launched, like a small volume halo car few people will ever get to see, let alone experience, first-hand. It’s 2026 now, and more and more of the small number of BeBoxen made must be succumbing to degradation and hardware failures. I hope everyone who has one takes good care of them, because these are some of the rarest, most coveted computers of all time. I’ve still never seen one, and here in Arctic Europe I most likely never will. Still, I remain hopeful. One day.
It’s always a special day on OSNews when Haiku has a new release. While OSNews was founded in 1997, it wasn’t until 2001, when Eugenia took over and relaunched the site, that we really got going. Eugenia came from BeNews, a popular BeOS news website, which shut down in the wake of Be, Inc’s infamous “focus shift” away from BeOS as a general purpose desktop operating system. BeOS continues to have a special place on OSNews ever since. Today marks the release of Haiku R1/beta6, the first official Haiku release in two years. As such, this new beta covers a monumental amount of progress since beta5, progress I’ve reported on diligently. The highlights of this new beta include a port of Firefox (including branding) and many of its forks, much improve support for Qemu, a new memory allocated largely based on the one from OpenBSD, and improved support for various filesystems. Of course, there’s a massive list of performance improvements, memory management changes, as well as a truly massive number of new application ports. It’s important to note, as I usually do, that while these Haiku beta releases serve as patches of calm in rough seas, Haiku is generally stable and capable enough that using the project’s nightly releases is usually a totally acceptable way of installing and running the operating system. If you’re not comfortable running nightly releases, however, and haven’t tried Haiku since the previous beta, you’re in for a massive overall improvement. Everybody loves Haiku.
Haiku has a Firefox port, but due to Mozilla’s trademark policies, it’s actually called Iceweasel. After some back-and-forth with Mozilla, the browser maker has no given Haiku permission to officially use the Firefox name for the port. But don’t worry, Iceweasel isn’t going anywhere. I plan to maintain both. The idea is to keep Iceweasel as the privacy-friendly, telemetry-free build, while Firefox will be the fully official, Mozilla-compliant build (with telemetry enabled, once I manage to fix the Glean rust issues). ↫ 3dEyes on the Haiku forums This seems like a nice solution, and happens to make sure Haiku users can actually choose between standard Firefox and what is essentially a more private “fork”. A great outcome.
Haiku has another buy month of development activity to detail, and there’s a big ticket item this time, even if the developers themselves don’t consider it so. The thing that should be the biggest news item this month is that the GSoC 2024 work to port “NVMM”, the NetBSD Virtual Machine Monitor (which runs on more than just NetBSD, despite the name), providing hardware-accelerated virtualization support for QEMU, was finally merged. Unfortunately it still doesn’t fully work, so it’s still disabled by default: hence, it’s only a minor news item, unfortunately. ↫ waddlesplash on Haiku’s website It may not work due to – so far – not well-understood problems causing any complex virtualised operating system to crash in a variety of ways, but since these problems seem related not to NVMM but Haiku itself, I still think this is a big piece of news. If the problems can be addressed, Haiku will have proper virtualisation, which is crazy to think about. There’s a forum thread in case you wish to help out with this effort. Other than this major news, there’s the usual list of small fixes and changes, including preliminary work on USB Ethernet support, which, when working, could be very welcome news for people whose onboard Ethernet doesn’t work with Haiku. The team also believes a beta 6 might actually be released this August, but once again I’d like to underline that Haiku’s nightlies work just fine, and you really don’t need to wait for a beta.
We’re a little deep into June already, but it’s only now that Haiku published its monthly progress report for May. There’s a bunch of fixes for drag-and-drop behaviour in Tracker, AVX512 support can now be enabled thanks to changes to the kernel’s FPU handling, some low-level changes were made for the Rust and Zig compilers, and further improvements were made to the boot process on the Raspberry Pi 5 (although a lot more work is needed on that front). There’s still no sixth beta since a few more blockers remain, but don’t let that stop you from installing Haiku – it’s stable enough as it is, sixth beta or no.
Big news from the Haiku forums: the Haiku ARM port is running on M1 Macs now. This is bare metal, no VM. m1n1+u-boot deal with the Apple-specific parts of booting, so we can boot UEFI images from USB like any PC. ↫ smrobtzz on the Haiku forums USB is apparently broken, but all 8 cores are functional, and it boots to a desktop. It’s still early days, for the ARM port in general and the M1 Mac port specifically, but it’s a great start.
The months, they don’t stop coming, so here’s another progress report for Haiku, our beloved successor to BeOS, the best operating system ever made. This past month the team’s added basic support for SMP on ARM64 (enough to use it in QEMU), the MIME sniffer’s internals have been overhauled for some serious performance gains, and a long list of smaller, but no less important or impactful, changes. Beta 6 still seems to be a ways off due to a number of unfixed bugs and an upcoming WebPositive release, but my usual spiel applies: you don’t need to wait for a beta to test Haiku. It’s stable enough as it is, and a nightly release will do you just fine, including updating to newer nightlies and application releases. This past month also saw which projects Haiku’s GSoC people will be working on. Two projects will focus on improving Haiku’s Bluetooth stack, including adding HFP profile support and support for HID devices, as well as general Bluetooth improvements across the board. The third and final project will focus on improving and expanding Haiku’s Devices application to turn it into a real management utility along the lines of those available on many other modern operating systems.
Another Haiku monthly activity report, but this time around, there’s actually a big ticket item. Haiku has been in a pretty solid and stable state for a while now, so the activity reports have been dominated by fairly small, obscure changes, but during March a major milestone was reached for the ARM64 port. smrobtzz contributed the bulk of the work, including fixes for building on macOS on ARM64, drivers for the Apple S5L UART, fixes to the kernel base address, clearing the frame pointer before entering the kernel, mapping physical memory correctly, the basics for userland, and more. SED4906 contributed some fixes to the bootloader page mapping, and runtime_loader’s page-size checks. Combined, these changes allow the ARM64 port to get to the desktop in QEMU. There’s a forum thread, complete with screenshots, for anyone interested in following along. ↫ waddlesplash While it’s only in QEMU, this is still a major achievement and paves the way for more people to work on the ARM64 port, possibly increasing its health. There’s tons of smaller changes and fixes all over the place, too, as usual, and the team mentions beta 6 isn’t quite ready yet, still. Don’t let that stop you from just downloading the latest nightly, though – Haiku is mature enough to use it.
And when a Redox monthly progress report is here, Haiku’s monthly report is never far behind (or vice versa, depending on the month). Haiku’s February was definitely a busy month, but there’s no major tentpole changes or new features, highlighting just how close Haiku is to a new regular beta release. The OpenBSD drivers have been synchronised wit upstream to draw in some bugfixes, there’s a ton of smaller fixes to various applications like StyledEdit, Mail, and many more, as well a surprisingly long list of various file system fixes, improving the drivers for file systems like NTFS, Btrfs, XFS, and others. There’s more, of course, so just like with Redox, head on over to pore over the list of smaller changes, fixes, and improvements. Just like last month, I’d like to mention once again that you really don’t need to wait for the beta release to try out Haiku. The operating system has been in a fairly stable and solid condition for a long time now, and whatever’s the latest nightly will generally work just fine, and can be updated without reinstallation.
January was a busy month for Haiku, with their monthly report listing a metric ton of smaller fixes, changes, and improvements. Perusing the list, a few things stand out to me, most notably continued work on improving Haiku’s touchpad support. The remainder of samuelrp84’s patchset implementing new touchpad functionality was merged, including two-finger scrolling, edge motion, software button areas, and click finger support; and on the hardware side, driver support for Elantech “version 4” touchpads, with experimental code for versions 1, 2, and 3. (Version 2, at least, seems to be incomplete and had to be disabled for the time being.) ↫ Haiku’s January 2026 activity report On a related note, the still-disabled I2C-HID saw a number of fixes in January, and the rtl8125 driver has been synced up with OpenBSD. I also like the changes to kernel_version, which now no longer returns some internal number like BeOS used to do, instead returning B_HAIKU_VERSION; the uname command was changed accordingly to use this new information. There’s some small POSIX compliance fixes, a bunch of work was done on unit tests, and a ton more.
Despite December being the holiday month, Haiku’s developers got a lot of things done. A welcome addition for those of us who regularly install Haiku on EFI systems is a tool in the installer that will copy the EFI loader to the EFI system partition, so fewer manual steps are needed on EFI systems. Support for touchpads from Elantech has also been improved, and the FreeBSD driver compatibility layer and all of its Ethernet and WiFi drivers have been updated to match the recent FreeBSD 15 release. Of course, there’s also the usual long list of smaller fixes, improvements, and changes. As for a new release milestone, beta 6 seems to be on the way. Not quite. There has been some discussion on the mailing list as the ticket list gets smaller, but there’s still at least some more regressions that need to be fixed. But it looks like we’ll be starting the release process in the next month or two, most likely… ↫ Haiku’s December 2025 activity report To be fair, though, Haiku’s nightly releases are more than able to serve their duties, and waiting for a specific release if you’re interested in trying out Haiku is really not needed. Just grab the latest nightly, follow the installation instructions, and you’re good to go. The operating system supports updating itself, so you’ll most likely won’t need to reinstall nightlies all the time.
The new year isn’t even a day old, and Haiku developer X512 dropped something major in Haiku users’ laps: the first alpha version of an accelerated NVIDIA graphics drivers for Haiku. Supporting at least NVIDIA Turing and Ampere GPUs, it’s very much in alpha state, but does allow for proper GPU acceleration, with the code surely making its way to Haiku builds in the near future. Don’t expect a flawless experience – this is alpha software – but even then, this is a major milestone for Haiku.
There’s a new Haiku monthly activity report, and this one’s a true doozy. Let’s start with the biggest news. The most notable development in November was the introduction of a port of the Go programming language, version 1.18. This is still a few years old (from 2022; the current is Go 1.25), but it’s far newer than the previous Go port to Haiku (1.4 from 2014); and unlike the previous port which was never in the package repositories, this one is now already available there (for x86_64 at least) and can be installed via pkgman. ↫ Haiku activity report As the project notes, they’re still a few versions behind, but at least it’s a lot more modern of an implementation than they had before. Now that it’s in the repositories for Haiku, it might also attract more people to work on the port, potentially bringing even newer versions to the BeOS-inspired operating system. Welcome as it may be, this new Go port isn’t the only big ticket item this month. Haiku can now gracefully recover from an app_server crash, something it used to be able to do a long time ago, but which was broken for a long time. The app_server is Haiku’s display server and window manager, so the ability to restart it at runtime after a crash, and have it reconnect with still-running applications, is incredibly welcome. As far as I can tell, all modern operating systems can do this by now, so it’s great to have this functionality restored in Haiku. Of course, aside from these two big improvements, there’s the usual load of fixes and changes in applications, drivers, and other components of the operating system.
Now this is a great initiative by the Haiku team: highlight a number of stale commits that’ve been without interaction for years, explain why they’ve stalled, and then hope renewed interest might grow (part 1 and part 2). Recently some discussions on the forum led to asking about the status of our Gerrit code review. There are a lot of changes there that have been inactive for several years, with no apparent interest from anyone. To be precise, there are currently 358 commits waiting for review (note that Gerrit, unlike Github and other popular code review tools, works on a commit-by-commit basis, so each commit from a multiple-commit change is counted separately). The oldest one has not seen any comments since 2018. Today, let’s have a look at some of these changes and see why they are stalled. Hopefully it will inspire someone to pick up the work and help finishing them up. ↫ Pulkomandy at the Haiku website Browsing through the highlighted stalled commits, there’s a few that seem quite interesting and relatively easy for a (new?) contributor to seek their teeth into. For instance, there’s a stalled commit to remove GCC from Haiku images built with clang/llvm, which stalled mostly because there are still other issues when building Haiku with clang/llvm. For a more complex problem, there’s the issue of how every menu in BeOS/Haiku is also a window, including its own thread, which means navigating deeply nested menus creates and destroys a lot of threads, that all need to be synchronised, too. If you want to get really ambitious, there’s the stalled commit to add initial 64bit PowerPC support. There’s more of these, of course, so if you have the skills and will to contribute to a project like Haiku, this might be a great place to start and get your feet wet. Now that these commits are back in the spotlight, there’s sure to be team members and regular contributors lined up to lend an extra hand, as well.
Another month, another Haiku activity report, and this time we’ve got a major change under the hood: a brand new guarded heap. The old guarded heap was suboptimal and had started to lag behind, so the new one attempts to rectify some of these shortcomings. So, to rectify these limitations, I rewrote the kernel guarded heap more or less from scratch, taking the old code into account where it made sense but otherwise creating entirely new bookkeeping structures, interacting directly with the page table and virtual memory systems, and more. This new guarded heap implementation frees physical pages when not in use, meaning that the “virtual memory reuse disabled” mode now runs for quite long periods of time (indeed, I could successfully boot to the desktop and run compile jobs.) It also prints more diagnostics when kernel panics due to memory faults inside the heap happen, which the old kernel guarded heap didn’t (but the userland one has always done). ↫ Haiku’s activity report for October The new guarded heap is optional for now, but Haiku is planning on releasing some pre-built test builds so users can start testing it out. Of course, this isn’t the only change or improvement from this past month – the list of changes is long, but there’s no real tentpole features here. Haiku’s development pace is still very much on track.
Another month, another activity report from the Haiku project. This past month, a lot of work went into the FreeBSD/OpenBSD network driver compatibility layer, opening the door to drivers using interfaces other than PCI or USB. Support for NFS4 took a bit of a hit with last month’s changes to VFS, and these have been addressed, and other aspects of NFS4 have been improved as well. On top of these two bigger items, there’s a list of smaller changes and fixes as well, but it’s been a calm month for Haiku so there’s less activity than normal. I’m not sure what to add in a second paragraph here. I’m nearing act 3 in Silksong? Is that relevant here? I doubt it, but I still wanted to mention it. Only a few loose ends in act 2 and on Hornet goes!
Another month, another summary of changes in Haiku, the BeOS-inspired operating system. The main focus this past month has been improving the performance of git status, which has been measurably worse on Haiku than on Linux running on similar hardware. This work has certainly paid off, as the numbers demonstrate. The results are clearly more than worth the trouble, though: in one test setup with git status in Haiku’s buildtools repository (which contains the entirety of the gcc and binutils source code, among other things – over 160,000 files) went from around 33 seconds with a cold disk cache, to around 20 seconds; and with a hot disk cache, from around 15 seconds to around 2.5 seconds. This is still a ways off from Linux (with a similar setup in the same repository, git status there with a hot disk cache takes only 0.3 seconds). Performance on Haiku will likely be measurably faster on builds without KDEBUG enabled, but not by that much. Still, this is clearly a significant improvement over the way things were before now. ↫ Haiku Activity & Contract Report, August 2025 There’s more than this, of course, such as initial support for Intel’s Apollo Lake GPU in the Intel modesetting driver, improvements to USB disk performance, a reduction in power usage when in KDL, and much, much more.
We removed ads from OSNews. Donate to our fundraiser to ensure our future! We all managed to survive another month, so here we are, with another monthly update from Haiku, covering the month of July. It’s been a rather short month, it being the middle of Summer and all, but there’s still some significant stuff in here. For instance, a whole slew of fixes arrived for su and other multiuser commands, mostly for the benefit of SSH sessions. A central theme in July seems to have been filesystems, as FAT16 was added to the known filesystem types in the Storage Kit, quite a few fixes were implemented for NFSv4, and a number of filesystems saw bugfixes to fix issues in rsync, and much more. Another central theme is apparently a port of DOSEMU, for which a number of bugfixes, changes, and improvements were implemented that could, in turn, also benefit other possible ports. And of course, there’s much, much more that happened, for which you’ll have to dive into the full progress report.
Haiku also survived another month of development, so it’s time for another roundup of what they’ve been doing. Considering it’s the height of Summer, it’s no surprise the list of changes is a bit shorter, consisting mostly of smaller bugfixes and minor improvements. A few standout changes are that cursors can now be properly scaled in HiDPI, the iprowifi3945 driver from FreeBSD has been replaced by the OpenBSD one because it performs better, and several improvements to how colour schemes work. waddlesplash refactored how control edge (borders, etc.) colors are computed inside HaikuControlLook (the class that renders UI controls under the default appearance), cleaning up a lot of convoluted computations. He also fixed some color handling in the progress bar control, and then along with nephele, refactored how control colors are used and computed across the system. The “Control background” color in Appearance preferences now has a new default and is much more properly used across the Interface Kit; under the default colors, renderings should be basically the same as before, but for users on “dark mode” or other custom color schemes, it will now be much easier to pick control colors. ↫ waddlesplash on the Haiku website There’s more, of course, so be sure to read the whole thing.
Submitted by