What's New in Haiku development
The Haiku source is continually built and released for testing purposes nearly every day. You can download and install these latest snapshots to check out the latest features and bug-fixes.
Be aware that nightly images may be unstable. Additionally, some packages included with official releases need to be installed separately.
If you're OK with this, you can find further instructions at our Nightly image page.
Only slighty bigger than 2017's "Kernel Debugging Camp" in Toulouse, this year's regular BeGeistert 031 (on its last day affectionately mottoed "The Dirty One") was held from November 1st to 4th in Hamburg.
As in the past when BeGeistert was in Düsseldorf, we had a nice conference room in a Youth Hostel, just with a slighty less nice bedroom. Toiletts and showers on the floor instead of in every room.
This evening a standard operating system upgrade has once again turned fatal.
Our infrastructure still depends on a single bare metal server at Hetzner which continues to be our downfall. This evening a (tested) OS upgrade failed resulting in maui going MIA. I requested KVM access to attempt repair of maui after it was missing for ~15 minutes, however we were stuck waiting almost 2 hours for the KVM from Hetzner.
Welcome to the tenth monthly report for 2018! PulkoMandy is busy packing and then travelling to BeGeistert, and most of the work these past two months was done by myself anyway, so, I’m covering for him once again. (Writing about yourself in the third person is fun!)
This report covers hrev52310-hrev52462 (~250 commits.)
R1/beta1! As you’ve probably already seen, heard, felt, … etc., Haiku R1/beta1 was released at the end of last month!
After nearly 6 years since R1/alpha4, Haiku R1/beta1 has been released. See “Release Notes” for the (lengthy) release notes, “Press contact”, for press inquiries … and “Get Haiku!” to skip all that and just download the release.
A small notification that we have updated our repository URL’s in preperation for R1 Beta 1.
This change will ensure that repository links remain consistant through R1 Beta 1 and beyond.
Time has come and a new monthly activity report arrived with it. It is the first time I write something this long in english. Enjoy!
This report covers hrev52141-52310.
Drivers Now that GSoC is over krish_iyer’s SDHCI MMC driver has been merged in master. There is still a lot of work to do and it is not enabled in automated builds yet, but should serve as a basis for any future related work.
At last, R1/beta1 is nearly upon us. As I’ve already explained on the mailing list, only two non-“task” issues remain in the beta1 milestone, and I have prototype solutions for both. The buildbot and other major services have been rehabilitated and will need only minor tweaking to handle the new branch, and mmlr has been massaging the HaikuPorter buildmaster so that it, too, can handle the new branch, though that work is not quite finished yet.
Hello everyone, We are in the final week of GSoC’18 program and yesterday our code has successfully merged. It got crashed in the first build because we thought we would add the code but disable the build currently but we didn’t test the case when device manager will try to find the driver in a certain directory which we hardcoded at the time of loading the module. So we just changed it to an OR condition where it won’t be able to find the driver binary but still be able to boot the OS in any case.
Hello everyone, this week we have tried to get the response from the command but unfortunately, it didn’t work out. In the meantime, I have submitted the code for review and PulkoMandy had already reviewed once. I have been going through Linux patches1 2 which are related to the issue we are currently facing.
I have done following improvements in the code
Disabled adding drivers to the kernel, removed statements from