You are probably aware of the existance of chkbfs. This tool checks the file system for errors, and corrects them, if possible. Nothing is perfect, so you might not even be asking yourself why a journaling file system comes with such a tool. In fact, it wasn't originally included or planned in the first releases of the new BFS file system. It was added because there is a real need for this tool and you are advised to run it after having experienced some BeOS crashes.
I love Haiku. That probably doesn't surprise anyone. I am phenomenally proud of the progress, both past and present that the project has made. I have lead the project since its creation, including running each of the WalterCon events, doing a great deal of public speaking, starting the non-profit, writing around 100 articles and editorials for the newsletter, fielding hundreds of emails, random phone calls and occasionally even writing some code. I have received a job offer because of Haiku and gotten back in touch with a number of old friends as a result of the publicity that Haiku (and, indirectly, I) has received. I have had the honor of meeting a bunch of the former Be crew and seeing the doubt and question fade as they saw what we had created. I had the distinct honor of being introduced by JLG.
I’ve decided to switch to an update every two weeks, which will hopefully prove more resilient to Real Life ™. I’ll also start being a little more selective about the changes I report to make it at bit less work for me to write, and a bit less work for you to read!
In brief, this period saw a lot of bug fixing work from the core contributors. A first firewire implementation was committed to the tree, Ingo completed Job Control support, Mail received a much-needed code cleanup, and Marcus continued the initial work on the AHCI SATA driver.
Read on for more on those, updates on mailing list discussions, and to find out how I managed to include a reference to Shakespeare…
On the 8th September, I attended a local Unix user group called HUMBUG, at the University of Queensland, Brisbane, Australia.
This was their Annual General Meeting, which was very much an informal gathering of 34 unix users and with the Haiku presence we had, we definitely made an impression; certainly more people know about Haiku than yesterday, and that’s gotta be a good thing.
Earlier that day when I was driving to the University, I got stuck behind this white hatchback, which had the license plate letters KDL.
During this summer I had the chance to improve myself, and work on the USB isochronous support of HAIKU. I wrote some code for every layer of the HAIKU USB stack: USBKit library, usb_raw driver, usb bus manager and most of all the uhci driver. I also spent/waisted some weeks with the usb_webcam media addon, but sadly with not success. Anyway here is what I did.
UHCI driver: Basically I added all the necessary code to handle isochronous transfer in both direction (in and out).
During this summer I was working under my mentor Jerome Duval’s guidance. This is the first time I tried to be part of the GSOC program.
I started reading as many documents about HAIKU as I can find before I was accepted on 11th April. I checked out the haikus’s source and built it and tested it on qemu. I was shocked by its clean and user-friendly desktop. I started reading its source after 1st May.
Hot on the heels of yesterday’s post, here’s the summary for last week’s activity in Haiku-land.
This week saw the driver for AHCI SATA controllers begun in earnest, the beginnings of job control support in the shell (and associated kernel stuff), a Sudoku game added to the image, and more bugs squashed.
There was also a discussion on the development mailing list about “hybrid” images of Haiku, allowing both GCC 2 and GCC 4 compiled apps to work on the same system.
A couple of months ago there was a debate on the mailing list about the openness of the Haiku project. I made the point that there was a lot of information in the public domain - SVN commits logs, bug updates, and a multitidue of mailing lists - the problem was that activity on these fronts was not obvious to more casual Haiku-watchers. I should have kept my mouth shut, because I ended up agreeing to write some summaries of this activity! This is the first of what will hopefully be weekly updates. Feel free to leave comments and suggestions below.
I have been documenting my progress on porting the WebKit project to Haiku on the Haikuware site, but decided to also post information here. You may want to read my previous blog article about this port and also the information at the WebKit bounty on Haikuware. Please consider donating to a bounty.
Before I started work on this port I asked in the #webkit IRC channel what the mimimum version of GCC that was required to compile WebKit. The general consensus was 4.0. So what does that mean?