BeOS & Derivatives Archive

20 years of Haiku

Dedication asks each of its adherents to have faith even as time and energy pass through from one year to the next. Dedication brings with it a variety of challenges, but also rewards. Dedication is something most people claim to have, but few readily exhibit it in the face of adversity. As of today, Aug. 18, 2021, the Haiku Project is celebrating two decades of dedication, marking the 20th anniversary of the founding of the Haiku operating system and the start of this ride to save, maintain, and expand upon the BeOS legacy it spawned from. Congratulations to the Haiku project and all of its contributors.

Haiku R1/Beta3 released

Poetry is in motion. The Haiku Project, its developers and team members announced the Haiku operating system released its third beta release, version R1/Beta3, July 25th, 2021. Version R1B3 continues the trend of more frequent releases to provide users and developers with an up to date and stable platform to work on. This release combines the best of Haiku’s history as a spiritual successor of BeOS and the hard work of a passionate community. It provides several new features and performance improvements that make Haiku even better. WebKit, the backend of the bundled web browser developed by the Haiku team, WebPositive, received multiple major improvements. This provides a good base for further improvements as well as an improved browsing and website rendering experience in WebPositive, which developers will continue to focus on for the next release, Beta 4 and as Haiku nears its first initial release, R1. Going from beta 2 to beta 3 is a giant leap if you haven’t been keeping up. Haiku is much farther along than people think, with the biggest drawback being, as always, that hardware support is going to be a mixed bag. Haiku is still every bit as clean, fast, and enticing as the original BeOS was over two decades ago, and I’ve scored two junkyard office PCs to see if I can get a proper Haiku box running.

Haiku boots to desktop on real RISC-v hardware

Hot on the heals of yesterday’s summary about recent Haiku news, we’ve got a big one – Haiku’s desktop running on real RISC-V hardware, the HiFive Unmatched. I finally managed to run desktop. Crashes was caused by unaligned access to framebuffer, access seems to require 16 byte alignment. I made some quick hack to enforce alignment in app_server when copying to front buffer, but it currently introduce artifacts. I don’t know why 16 byte alignment is required, radeon_hd driver works fine on Acer W500 tablet without alignment tricks. This is a big milestone.

Haiku’s latest activity report, more RISC-V news, and a small delay for beta 3

A random collection of Haiku news today – starting with the latest activity report. With the release of beta 3 creeping every closer, there’s a lot to report in this one, from improving POSIX support, to improvements to the Intel video driver, to work on the bootloader, and a lot more. Secondly, there’s news on the RISC-V front. Two months ago, a lot of progress was made on porting Haiku to RISC-V, and earlier this month, the Haiku project decided to really support this effort by buying RISC-V hardware and donating it to the developer in question. The HiFive Unmatched board has made its way to the developer by now, so expect a lot more progress on this front in the future. Lastly, the project has decided to push back the release of beta 3 by one week. There’s one remaining nasty bug in the WebKit port, and since the team wants to make sure the browsing experience is the best it can be, they’ve decided to give the developers a bit more time to iron out this final bug.

Haiku sets R1/Beta3 timeline and release date

If all goes to plan, Beta 3 will be released sometime after the 24th of July. Note that the release will only happen when everything is ready, so there are no final dates and the timeline may change to account for delays. The Promotion Team is currently investigating Beta3 DVDs and USB sticks to order: the Inc. has been notified and quotes have been requested from two possible services. A lot of other software projects would’ve called these betas final releases. Haiku is a lot more stable, capable, and usable than the beta label indicates.

Haiku developer ports Haiku to RISC-V

Have you ever want to follow along as someone ports an entire operating system to a new architecture? Well, now you can! Haiku developer X512 is porting the Haiku operating system to RISC-V, and is posting regularly in a long and detailed ongoing thread on the Haiku discussion forum, detailing his successes and struggles along the way. He’s already quite far along: Most things are working, system is quite stable. Now applications crash show error dialog instead of KDL. Also after removing no more needed workarounds (fully allocate stack memory instead of allocating on demand by page fault handler) memory usage was reduced. It’s fun and informative to read the whole thread from the beginning until today, and see the progress unfold as if you’re sitting right next to X512.

When you have too much memory for SheepShaver

When I first got my 133MHz BeBox (not new, sadly), it had “only” 32MB of memory and it had four more SIMM slots to fill. While Be only officially supported 256MB of RAM, I was blissfully ignorant of that, bought an additional 256MB of memory in four equally sized 72-pin SIMMs and installed it for 288MB of RAM. (It can actually take up to 1GB, I later learned.) Nice, I said! And then SheepShaver never worked again. This is basically OSNews catnip.

Haiku activity report – February 2021

Another month, another Haiku activity report. It was less busy this month, so there’s nothing that really jumps out at me as a major fix or improvement. I’m going to highlight the first listed item, since fixes in software delivery are always welcome. Andrew Lindesay continues his work on cleaning HaikuDepot sources and removing a custom-made List class to use standard (BeAPI and C++ stl) containers. There were some regressions in the process, that were found and identified. Haiku’s steady stream of fixes and improvements continues.

Haiku activity report – January 2021

Another month, another Haiku activity report. January was a busy month for OSNews’ favourite operating system project, with a lot of love sent the way of the various ports to other architectures. Work has been done on the ARM and RISC-V ports, but also on platforms you might not expect in this day and age: SPARC and PowerPC. While some may question putting any effort into these alternative platforms at all, that’s a shortsighted position – work on other platforms often aides in uncovering and fixing bugs in the code for your main platform. It also prevents code from becoming more platform-dependent than it needs to be. Amid the long list of other improvements, the one that stands out is merging support for SD/MMC cards. The SD/MMC drivers are merged. It is now possible to read and write SD and SDHC cards using controllers compatible with the SDHCI specification. This is one of those things that will make it easier to transfer files to and from your Haiku installation.

Mesa 21.0 is now working with Haiku for software OpenGL rendering

A number of patches worked on for Haiku OS back for Mesa 20.x were freshened up and with some extra tweaking and code cleaning those patches have now been merged for Mesa 21.0. This includes factoring out a lot of the OpenGL legacy dispatch code and a lot of cleanups around the Softpipe driver handling. With Mesa 21.0-devel as of today, it’s at least enough where Mesa Git can now be built on Haiku OS and yield working OpenGL rendering with the LLVMpipe software. Neat, and a testament to Haiku being in a far better state than many people seem to think.

Haiku makes progress on ARM port

There’s a new Haiku activity report, and there’s been a lot of activity over the past two months. My pick this time is progress on the ARM port. tqh and kallisti5 are working on the ARM port. The bootloader is now running mostly fine in UEFI mode but there is some work to be done to set up the MMU before handing control over to the kernel. There are problems related to the “hardfloat” and “softfloat” ABIs on ARM, however. Until now we had worked with the “hardfloat” ABI for Haiku, assuming floating point hardware was available (as is the case on any modern CPU we could reasonably target). However, the EFI firmware does not properly handle these registers, and this seems to result in some confusion when passing data to and from the firmware. We may need to build the bootloader in soft-float mode (not using the hardware floating point processing), but that in turn creates some difficulties with properly configuring gcc. On 64bit ARM, the floating point support is not optional, so it may be easier to move forward with the 64bit port first. The ARM port is important for the future, since desktop and laptop ARM hardware may become far more available than it is today.

Rust on Haiku: the case of the disappearing deceased threads

For a long time I have been maintaining the build of the Rust compiler and development tools on Haiku. For this purpose, I maintain a separate tree with the Rust source, with some patches and specific build instructions. My ultimate end goal is to have Rust build on Haiku from the original source, without any specific patches or workarounds. Instead we are in the situation where we cannot build rust on Haiku itself (instead we need to cross-compile it), and we need a customization to be able to run the Rust compiler (rustc) and package manager (cargo) on Haiku. This summer my goal would be to find out the underlying issue, and fix it so that the patch will no longer be necessary in the future. Let’s go! There seems to be quite a bit of excitement around the Rust programming language, so it makes sense for Haiku to jump on the bandwagon as well.

Haiku makes progress on ARM port

The July activity report from the Haiku project is out, and there’s a lot of stuff in there. My favourite highlight: kallisti5 continued work on the ARM architecture, specifically the ARM64 EFI bootloader. EFI CPU code was refactored to be architecture-specific, allowing CPU init code to be properly called, further progressing the EFI bootloader, which is now building and running. I love the progress on ARM, since ARM seems to have a bright future – Haiku needs to be there.

Haiku repository files and identifiers

Software on a computing platform such as Haiku is typically distributed as a package. Without a packaging system it would be hard for users to install software and because software often depends on other software, the chain of dependencies would be difficult for a user to resolve themselves. To orchestrate the distribution and management of the packages, Haiku has a packaging system which consists of applications, online tools, on-host tools and software libraries. One aspect of the packaging system is the coordination and identification of repositories. An overview of the inner workings of package management on Haiku.

Resurrecting BeIA

Did you ever wonder what BeIA really was? A lot of people talked about BeIA back in the days Be, Inc. was still developing its OS for internet appliances, but after Be, Inc. closed its doors, BeIA vanished as well. A thread over on the Haiku discussion forums – which began as a talking point for how Haiku could recreate a BeIA style concept – turned in to a treasure trove of BeIA information, including examples of BeIA running and an overview of some of the process of building BeIA distributions. This video shows it all in action, including BeIA running under emulation. There’s also a wonderful video shot in Be, Inc’s offices where a Hungarian UG member gets a tour and shown BeIA hardware, with terrible framerate and resolution, but well worth checking out.

Haiku monthly activity report for May and June

After the release of the second beta a few weeks ago, Haiku continues its steady pace of improvements and fixes. A few highlights from the work done since the beta release: Korli also worked on improving support for modern x86 CPUs, including the xsave instruction, and enabling use of AVX which requires saving more CPU registers during context switches. A new version of HaikuWebKit has finally been released after help from KapiX and X512 to fix the remaining bugs. It uses a lot less memory, crashes less often, and has better support for modern website. There is ongoing work for further updates and improvements. There’s a lot more in there, so if you have beta 2 running, be sure to update it.

Haiku R1 beta 2 released

The second beta for Haiku R1 marks twenty months of hard work to improve Haiku’s hardware support and its overall stability. Since Beta 1, there have been 101 contributors with over 2800 code commits in total. More than 900 bugs and enhancement tickets have been resolved for this release. There’s so many improvements in this new release that it’s hard to pick favourites. Since many Haiku users basically use the operating system on a rolling release basis through online updates, it’s easy to lose track of what’s new between beta and 2. I have a VM for Haiku that I regularly update and use, and it’s remarkable just how stable and fast Haiku has become over the years.

BeOS: the alternate universe’s Mac OS X

You’re likely familiar with the old tale about how Steve Jobs was ousted from Apple and started his own company, NeXT. Apple then bought NeXT and their technologies and brought Jobs back as CEO once again. However, Jobs’ path wasn’t unique, and the history of computing since then could’ve gone a whole lot different. In 1990, Jean-Louis Gassée, who replaced Jobs in Apple as the head of Macintosh development, was also fired from the company. He then also formed his own computer company with the help of another ex-Apple employee, Steve Sakoman. They called it Be Inc, and their goal was to create a more modern operating system from scratch based on the object-oriented design of C++, using proprietary hardware that could allow for greater media capabilities unseen in personal computers at the time. Not much new information in here for the regular OSNews reader – and these articles get published about once a year – but it’s always nice to see the best operating system of all time get some love.

Haiku’s Paladin C++ IDE gets an overhaul

Paladin, a C++ development IDE for Haiku, has been updated with several new features and bug fixes. Some of the new features: • Quick Find window (Alt+F) – find files in a project by name, or abbreviation (E.g. qfw gives you QuickFindWindow.cpp) • All the Samples from the online Haiku dev book are included as Template Projects • Running applications ‘as logged’ now gives a live Monitor Window showing the streamed contents of stderr and stdout, using a new and reliable posix CommandThread wrapper (a ‘Preview Feature’ that, if popular, may end up back in Haiku proper for others to use) • Automatic switching of Haiku libraries when you open the same project from 32bit and 64bit Haiku versions • Running a build now generates compile_commands.json as used by other software • All new backend functionality now using a TDD approach to improve quality and avoid regressions • User requested modifications are prioritised, with a delivery average of 2 weeks There’s an update video available so you can get a better feel of the new features, and you can download and install Paladin through HaikuDepot. The code’s available under the MIT license at GitHub.