Haiku is a new open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.

Fundraising 2014

Goal: $35,000
  $13,754

WHAT'S NEW IN HAIKU DEVELOPMENT

The Haiku source is continually built for testing purposes. You can download and install these latest snapshots to check out the latest features and bugfixes.

Be aware though that they may be unstable. Additionally, Web+ and some other packages have to be installed separately.

If you're OK with that, you'll find further instructions at our Nightly image page.

NFSv4 client: midterm report

Blog post by Paweł Dziepak on Wed, 2012-07-11 16:58

Having implemented mandatory hooks by quarter term I had good base for implementing other operations like write, rename, create, etc. Moreover, improvements in file system migration and user ID mapping. Apart from that, file locks required most work, since they are both more complicated than other NFS operations and Haiku VFS originally did not allow the file system to handle them its own way.

cpuidle: midterm report

Blog post by yongcong on Wed, 2012-07-11 13:04

With the good preparation in quarter term/bonding period, I have completed the generic cpuidle kernel module, native intel cpuidle module and cpuidle driver(for states/info reporting). By original plan, these tasks will be all completed by the end of 3/4 term...

x86_64 port: midterm report

Blog post by xyzzy on Wed, 2012-07-11 11:08

Since my quarter term report I have made a great deal of progress. The boot loader x86_64 support is finished, and the kernel can now be booted to the point of searching for the boot volume. A screenshot of this:

QR Encode your KDL Output!

Blog post by mmlr on Sun, 2012-07-01 21:27

Usually when you arrive in KDL (Kernel Debugging Land) it means that something bad happened. KDL provides a lot of tools to investigate what might have taken place. Still, it is quite possible that, even though you have that arsenal of tools available, you may not be able to immediately make sense of what is going on. In that case you ideally either continue debugging yourself or you write up a nice bug report over at the Haiku bug tracker so that someone else can take a closer look.

He's back, back in the Haiku groove!

News posted on Sat, 2012-06-30 16:49

Ok it hasn't been years since Michael was here, on IRC passin' his time away.
To the left and to the right, commits towering to the sky.
It's outta sight in the dead of night
Here he is, again in this project, with a fistful of keystrokes
And baby, you better believe.

He's back, back in the Haiku groove!
He's back, back in the Haiku groove!
(Ok, enough ripping off KISS lyrics)

Michael Lotz has been casually making commits in his KeyStore feature branch! First as a reminder to everyone, as Michael explained the KeyStore API will be able to "securely manage keys, passwords, certificates, etc. in a central place and generic way (so that it can be used by other applications as well)". More details on its design and functionality are mentioned in Michael's blog. As you can imagine the KeyStore API will add much appreciated functionality to Haiku, specifically in the area of managing wifi connections.

BFS Partition Resizer: Quarter Term Report

Blog post by ahenriksson on Mon, 2012-06-25 10:58

For the 1/4 term milestone, my goal was to have inode-moving working. This is mostly completed, you can view the code at http://web.student.chalmers.se/~andrhen/move_inode_v2.patch

For this period, I have the following things planned:

Allocation of new block positions: I have a good grasp of what needs to be done for this, and it's not a lot of work.

Moving file data: Last week I thought I had this nailed down, but it turned out to be a little more involved than that. Still, there has been some good progress made, and I'm sure it'll be completed within the period.

Doing the actual resizing: This step involves a few sub-steps: traversing the file system to move things out of the way, possibly moving the file system journal, resizing the block bitmap and updating the file system header. None of it should be that complicated (in theory), however it's likely that the more thorough exercising of the rest of the code will reveal problems with it.

Testing: I obviously test code as I write it, but I probably won't have time for a more rigorous approach in this period. I have a lot of time allocated for that in the next period, so it's not a disaster.

As it looks right now, things seem to be on track with the timeline in my proposal (which is actually not that great, as the timeline was a bit pessimistic).

NFSv4 client: quarter term report

Blog post by Paweł Dziepak on Sun, 2012-06-24 18:09

I have already implemented all mandatory hooks (and several others), what means that NFSv4 client now allows to browse directories and read files on remote filesystems. Last several days I spent on improving the existing code and supporting some less usual NFSv4 describes, that includes reclaiming share reservations, support for server migration and volatile filehandles. I also needed to deal with NFSv4 that do not provide file's inode number, that was solved only partially since proper workaround will be much easier to implement when file metadata and directory contents are cached.