Today I woke up to the news that Haiku was mentioned at MYCOM Journal, a Japanese IT related news site, in a regular column known as OSX Hacking. This time the author was playing with VirtualBox and he tried running Haiku on it. Well, he did succeed, but the speed was not up to the expectations. GLTeaPot ran at the incredible speed of 1.3FPS (yes, you read right!), on a first generation MacBook 1.
Hopefully, you noticed that Trac, our bug and task tracker, is back and has a new home: https://dev.haiku-os.org. We switched our hosting provider and now everything works well and Trac is stable (as far as I know ;). Did anything user-visible change? Yes. The components (categories) were reorganized. Our developers needed components resembling our source code tree. Since this wouldn't work very well for non-technical users (indeed we don't have many of them, yet) or users who don't know which component is affected we also created broader categories like "
We finally deployed the new website. Waldemar fixed at the last minute a bug that we discovered in one of Drupal’s module, and we then asked Takidau to change the DNS settings. It was a long road. How long did it take? A bit more than 6 months? Much longer than I would have expected, I have to admit. But I think it is a good start. As some have already pointed out on the Haiku mailing list, there are still a few areas that need to be tweaked.
Today I presented the first (out of three) Google Tech Talks scheduled for the following weeks. The reception I got from other Google engineers was really good and, more than that, they gave me lots of feedback that I will apply to the following presentations. Seeing the reactions made me reach the conclusion that we are in the right path and even when considering a highly technical audience, the simplicity we are trying to achieve with Haiku got the interest of several engineers.
Today I finished making all the changes that had to be made after dropping the Drupal authorship.module; it was much more work than expected (I should have known), as all the articles belonging to authors that did not have an account had to be edited one by one. Well, it's done now, so all there is left before we can finally do the migrations is creating two pages: Contributing Content and Spreading the Word.
I recently looked into why BeIDE’s interface did only have green squares where its icons should have been (bug #313). The function importing the client’s bitmap data did not work correctly, and while playing with it, the app_server suddenly crashed, and continued to do so in a reproducible way.
How was this possible? Bitmaps are located in a shared memory pool between the app_server, and an application. Unfortunately, the app_server put those bitmaps into arbitrary larger areas, and put the structures managing that space into those areas as well - like a userland memory allocator would do.
Since a few days, we have a working APM driver in our kernel. APM stands for Advanced Power Management. It’s a service as part of the computer’s firmware commonly called BIOS in the x86 world. The latest APM standard, version 1.2, is already almost 10 years old. Today’s computers do still support it, even though the preferred method to have similar services (among others) is now ACPI, or Advanced Configuration and Power Interface.
If you’ve used BeOS, you’re probably familiar with the above message when trying to unmount a volume. From time to time, some application keeps accessing a volume, and you can’t determine which application that is. It might be caused by a running live query, but it might also be caused by buggy background applications that forget to close a file.
I’ve just given you control over your volumes back again in Haiku: you can force unmounting such a volume – applications still trying to access it, would get an error back.
My official employment at Haiku has ended now. I wanted to thank you for all the donations that made this possible. In retrospect, it were pretty busy months for Haiku, I think I have committed over 600 changes during that time, lots of minor ones, of course, but also a few bigger ones.
In case Haiku runs on your system, you should now be at least able to experience uptimes of several hours, depending on what you do, of course :-)
Instead of completing the paging implementation, I got distracted with a couple of crashing bugs that showed up while testing Haiku, and they kept me busy for the last few days. Strangely enough, I could reproduce each bug easily only on different systems.
At least, I could now run Haiku with BitmapDrawing and Pulse in the background for over an hour (after which I shut it down myself). While playing around with it, I found some weird behaviour with the Backgrounds application which I am currently working on.
