Just thought we’d let you know that, Haiku-Files is now hosting GCC4 builds of Haiku in both RAW and VM image formats.
You can obtain these builds in the usual directories and we’ve updated the RSS feeds as well.
We’ve also fixed the VMX file that is distributed with the pre-alpha images to have the correct virtual hard disk name. Sorry for this oversight, I wasn’t aware of it, until I was playing around with VMware Fusion last night.
Greetings one and all!
I am Obaro Ogbo, one of the students selected for GSoC 2009. I also use the name nastee on irc and on Haiku Bug Tracker. I am a 3rd year student of Computer Science and Technology at Bells University of Technology Ota, Nigeria, and it appears I’m the first ever Nigerian GSoC student :-).
I began programming with Java, then learnt C before studying C++. I’ve done little PHP and Perl coding, however I’m learning Lisp presently. I participated in the Nigerian ACM/ICPC in 2007 and 2008 where my team came 3rd and 2nd respectively.
I live in Honolulu Hawaii, I enjoy Surfing, Swimming, Sun and Code. I am working on my BS in Computer Science at the University of Hawaii at Manoa and minoring in Geography. Next year will be my senior year. I have taken courses in concurrent programming as well as networking. Next year I will be taking an operating systems course. I also have some experience in machine architecture and optimization. My current side project is writing an application for the Geography Department, that is a complete suite of tools for stereogrammetry. My professional work has been work on an electronic medical health records system based on the United States Veterans Affairs VistA system. I have more recently worked for Nanopoint Imaging Inc. working on live cell imaging and microfluidics software.
Personal Profile
- Ma Jie
- Brief bio
My name is Ma Jie, And Jie is my given name. I'm a senior college student from China. Although not majored in Computer Science, I still love to do computer programming in my spare time. I have a National Computer Rank Examination certificate on computer network technology and got third prize of a national Java programming competition. The PoorMan server of Haiku is my first contribution to the open source world. I learned a lot from it, and I think it's time to contribute my knowledge back.
Project idea information
- Project title
Implementing ZeroConf support for Haiku with mDNSResponder- List of project goals
- porting mDNSResponder to Haiku
- a mDNSResponder configuration preflet, which can be integrated into the network preflet in the future
- a services browser and notifier, which may be integrated into the Deskbar
- making PoorMan server utilize the ZeroConf network
- writing test cases and running the tests
- Project description
There are two major implementations of zero configuration networking, Avahi and Apple's Bonjour. mDNSResponder is the underlying component of Bonjour. There are several reasons for me to choose mDNSResponder as the Haiku's ZeroConf engine. First, as Avahi is mainly designed for linux and BSDs, it uses GNU Autotools, while mDNSResponder uses handmade makefiles. Since Haiku's build system consists of a lot of Jamfiles, mDNSResponder will be easier to integrate into the source tree. Second, Avahi lacks porting directions. Finally, Haiku prefers Apache license that is more compatible with Haiku's MIT license to LGPL.There may be some difficulties when porting mDNSResponder to Haiku, because the cross platform support is abandoned and some gcc incompatible codes was added to the sources. I need to fix the broken codes during the porting procedure. mDNSResponder will run like other Haiku components. A server runs in the background and clients that want to use the ZeroConf services can communicate with the server by a library.
Personal Profile
- Johannes Wischert
- Brief bio - I'm a computer science student living in Germany. I'm 25 years old now. I wrote my first program with 8 or 9 years or so and never stopped since then... After my studies I want to work somewhere in the embedded systems development but by now I enjoy my studies and take my time to finish.
Project idea information
- Project title - Port the Haiku Kernel to ARM-Architecture
- List of project goals -
- generic u-boot Bootloader using the u-boot apis as far as possible to ease porting to other platforms that use u-boot
- Kernel that runs on the arm-processor and supports all applicable features that the x86 kernel has
- Device driver for at least the SD-card and the Serial-Port
- Working system running on a Beagleboard or similar device
- Project description -
- To get the system running on an ARM-CPU we first need a working Haiku ARM toolchain to compile the code I already got the toolchain to run and produce working binaries (tested under qemu) so this part of the system already works more or less. see: https://dev.haiku-os.org/ticket/3633
- After that done the next step is the boot loader. Since the beagleboard I want to target already has "Das U-boot" bootloader installed I decided to use it to get the kernel loaded. Using the u-boot loader has some advantages since it already provides all the important data and functions for loading the kernel like builtin serial drivers and drivers for all kind of memory to boot from (including a TFTP client) these functions are exposed by a simple platform independent API. By using this API an architecture independent kernel loader could be build, so that porting to other architectures that use u-boot would be much easier.
- The loader would run as a standalone application on top of u-boot to use it's features and then switch to direct access to the hardware to run the kernel.
- To allow u-boot to boot the kernel I could either include bfs in u-boot or implement the bfs in the loader programm. If the bfs code is in the loader no change to u-boot is needed so I will probably take this way since changing the u-boot always has the risk to brick a device.
- I know that this is not everything and I will probably have to ask a lot of questions to get everything right ;)
- I must admit that I don't know to much about the ARM internals, yet so I can't give much details about how I will port the MMU dependent stuff etc.
- The device drivers for the serial-port and the sd-card are quite straight forward to implement, since they are interfaced directly by the processor (at least on the beagleboard) and there are a lot of existing open source drivers (of course we would have to pay close attention to the licenses etc...)
- Since the beagleboard does not have an isa or pci bus it could use code similar to the m68k port to put the onboard devices in the pci bus. Even better would be to write a sort of bus system for the onchip devices this would also help to port to other devices that do not realy have a bus system like many other embedded devices.
- The next steps would be to write a driver for the onchip usb-controler and a Framebuffer driver if the porting goes much faster than I think ;)
- Why do you want to work on this project?
- I love the whole concept of Haiku and would love to see it run on embedded hardware like all these planned linux+arm netbooks. Since ARM-CPUs are used in so many different devices and most of these devices are multimedia devices like netbooks/mediaplayers/smartphones it would make sense to port Haik as an multimedia OS to these devices.
- I already have experience in embedded programing for example I ported an OS from the MSP430 to the SuperH Architecture for university (it was a nano kernel OS called SmartOS there is a wiki about this project but for whatever reason they have the interesting parts hidden http://www5.informatik.uni-wuerzburg.de/snow5xoops/modules/dokuwiki/doku.php? ) so I know a bit about all the problems that could arise.
- I know porting such a complex project is quite difficult but I have the time to concentrate on this project and it's not the first embedded project I work on (but probably the biggest ).
- Other projects I worked on were a device driver for the r4ds flash card to use it under DSLinux on the Nintendo DS and some other smaller stuff like a stepper motor controler board that was controlled by an MSP430.
- I know that this project is not really helpful to get closer to the first alpha release of haiku but I think an ARM port would be a interresting addition to the Haiku project and perhapse attract some more developpers.
Personal Profile
Maxime Simon
Brief biography:
I am currently in my third year studying Computer Science at Rennes 1 University in France.
I have some experience with development thanks to several academic projects, chiefly written using the Java and C languages.
Our first big project used an obscure language called “oRis”, an object and agent-oriented language developed as part of the doctoral thesis of Fabrice Harrouet. The project’s objective was to design a simulation of pathfinding robots, with basic behaviour and capable of cooperating to achieve goals in a virtual maze. This project enabled us to learn how to manage a project using Subversion, and how to organise its development.
The project was managed at this page:
http://code.google.com/p/csr/
Hello world !
As you know, I am one of the selected students for this year summer of code. In this post I will introduce myself and give some details about my project.
My name is Adrien Destugues, some of you may know me as PulkoMandy as i’ve been lurking on the irc channel and mailing lists for some time. I already applied for the Summer of Code and Haiku Code Drive last year but unfortunately I was not selected. This year it went better :)
I’m studying electronics and computer science at the ENSSAT (École Nationale Supérieure de Sciences Appliquées et de Technologie), in Lannion, France. I used to run BeOS as my main operating system for some time, but I now switched to Linux. I have a running Haiku install on my hard disk, but as my network card is not supported, I don’t use it much for everyday work. I hope this will change soon.
Context
Imagine the release just got out the door; what needs to be ready at this point to get everything running smoothly ?...
Newcomers
We need some structure to welcome newcomers (developers and others) effectively. I think many -- everything is relative -- people with various skills will come and may ask things like :
- Where can I help ?
- I want to port [insert favorite software from linux] !!!!
- Many others...
We should make sure that we can “steer” them to the correct teams (according to their tastes).
Greetings,
I’m proposing myself as a release coordinator for the upcoming Alpha Release, and here are the highlights of the plan.
First, this plan shouldn’t be applied before those conditions are met :
- the LiveCD works quite good (with no major issues left). My understanding of that topic is that we still need the FS overlay (that allows attributes over iso9660) to support live queries. If there is anything more to add to this point, please comment. Plus, the ioscheduler should be tweaked to enhance the user experience using that media.
- all the criticals (blockers) issues already identified are fixed. I see that a lot of them have already been taken care of; that's good! :)
So basically, my plan tries to moderate the pressure on the developper workforce while at the same time optimize the benefits from the release (attention from the community at large, etc..)
What I propose is to set a condition list, that when all met, will trigger the countdown. So here is the basic timeline I propose :
According to my resume, I’ve been contributing to Haiku since 2002. I don’t remember how I determined that start date, and GMail is only five years old so searching that does not provide me with an answer either. What I do know is that I feel a strong connection with this project. Which really makes it all that harder to part.
I remember I started by writing a naive proposal about internationalization back when this was still OpenBeOS. You should know that at the time I was sixteen years old, so I never really knew BeOS, and I just came from the translation team from KDE. I left that project in search of something bigger, more integrated, more … I think we have all been there. BeOS seemed like a materialization of that dream. Only, Be Inc. already turned into ashes when I started my quest. A bunch of silly coders with a vision were determined to continue that dream. Little did they know that seven years later their code would boot on many machines - even though mine right now seems to be left out of the fun. My proposal on internationalization, however, never came to materialize.
