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.

x86_64 port: final report

Blog post by xyzzy on Tue, 2012-08-28 09:57

Since the three-quarter term report, I have continued porting userland servers and apps. The app server is fully functional, as are Deskbar and Tracker and a few other apps. I also cross-compiled all of the basic development optional packages (GCC/Binutils, autotools, make, etc.) for x86_64. Another screenshot showing the current state of things is below:

cpuidle: final report

Blog post by yongcong on Mon, 2012-08-27 12:18

the last quarter term is mostly spent on acpi cpuidle driver implementation. I also spent about 2 days to adjust the cpuidle framework so that the cpuidle generic module is loaded by lowlevel cpuidle driver, while the later will be loaded during boot up either by bus enumeration or calling get_module() manually. I also tested the power after acpi cpuidle driver is finished. The result is as good as intel native one. Since all the goals defined in my proposal are achieved, so the project is successfully finished.

Here I want to summarize the status:
generic cpuidle
generic cpuidle module is implemented which can be used on all cpu architectures;
x86 cpuidle driver
On x86 platform, we support intel native cpuidle driver and acpi cpuidle driver. The previous one make fully use of intel mwait extension support on intel newer cpus such snb, ivb or latter, since it won't touch the complex acpi part, it's preferred if the HW supports. The acpi driver is our last choice.
power saving number
On my T420 laptop, it saves about ~2.5watt
main limitation
we don't support old platform which doesn't have ARAT(always running apic timer). To support such platform, we need to enhance haiku's timer subsystem

I'd like to continue all the related power saving work in haiku such as to find and remove all the unnecessary wakeup source, to enchance haiku's timer subsystem mentioned above. I may also work on some acpi related driver, the acpi is complex but I learned a lot about acpi during this summer ;)

Finally I'd like to thank tqh for his guidance, carefully code review and kind help about ACPI related topics, thank haiku for giving me the chance to code for such a clean and beautiful operating system. I also owe a great deal to many haiku experts for their immediate answers on IRC or great suggestions on mail-list. The last thank belong to Google :D

OpenJDK port: final report

Blog post by hamish on Sun, 2012-08-26 23:43

Since my three-quarter term report I've been working on adding audio input support to the jsound port and fixing various bugs in the JDK. Since the AWT/Java2d and jsound ports are now completed, my goals for the summer have been accomplished! The OpenJDK port is now in a fairly usable state, and community members have been using it to run some large scale Swing apps such as NetBeans and ThinkFree office.

The next thing I would like to do is merge my work in to the Haiku port repository at the OpenJDK project. From there I'd like to look into the possibility of acquiring access to the Java TCK, which will allow for comprehensive testing of the port. This will no doubt uncover many bugs and keep me busy for a while. Here are some other possible areas of expansion for the future:

NFSv4 client: final report

Blog post by Paweł Dziepak on Sun, 2012-08-26 18:46

Since three quarter term I've added NFS-level support for named attributes what means that virtually all important NFS version 4 feature are now implemented, as I described them in my blog posts during the coding period. What still needs to be done is to improve support of Haiku's extended attributes and a lot of bugfixing. There is also a room for performance improvement and several possibilities to organize code in a better way.

Haiku Down Under 2012 Report

Blog post by Sikosis on Sun, 2012-08-26 06:41

If anything could go wrong -- it did go wrong at the Fifth Annual Haiku Down Under Conference for Users and Developers, held at The University of Queensland, Brisbane, Australia on 19th August, 2012. At least, that's how it initially played out.

GP South Building at The University of Queensland

Two contractors, each for two months!

News posted on Mon, 2012-08-20 21:26

That's right -- Oliver Tappe and Ingo Weinhold have been accepted for individual contracts![1, 2] Each of them will be working for two 160 hour periods. That adds up to an additional 640 hours of dedicated HAIKU development time for a total cost of €8,000 EUR. The area of focus will be Haiku's package management. (See A brief summary of HAIKU's package management. for an explanation of how package management will work.)

Hopefully, these contracts will start in Dec. 2012. Given the delay between this announcement and the expected start date, there will be another reminder upon the actual start of the contracts. (Or if something unexpected comes up, an announcement for that.)

As both expect to start at the same time, this could be a tremendous productivity boost. Not only will they both have the opportunity to dedicate large blocks of time specifically for developing Haiku, but each of them will be working on the same project! Both of their minds would be in tune with their immediate tasks at hand and the larger picture. That would make bouncing ideas (and obstacles) off of each other that much more effective. It is specifically the nature of Haiku, Inc.'s contracts that fosters this type of cooperative development in a for-pay scenario. Instead of simply rewarding the completion of a product (without care for the implementation or the implications of future works), these contracts allow the developers to ensure their contribution is implemented with the future of the project in mind.

As there are over 2,000 open tickets for R1, there clearly are numerous areas of Haiku that are in need of improvement. However, so long as the contract proposals are for R1 items, it is not the practice of Haiku, Inc. to give preferential treatment to particular projects. Haiku, Inc. is always interested in receiving contract proposals.

If you appreciate these contracts and want to see additional contracts to accelerate the development of HAIKU R1, then spread the word and donate today!

NFSv4 client: three quarter term report

Blog post by Paweł Dziepak on Mon, 2012-08-06 22:09

I've recently been working on caching in NFSv4 client. It was essential in order to allow the client to be comfortably used. I can gladly say that the traffic generated by NFS client has been greatly reduced, thanks to metadata, directory, lookup and file caching. I've also implemented support for open delegations which, though not always available, allow the client to perform virtually all file operations without immediate server participation.