My experiences in contributing to minix 3

Why this post?

In this post I am going to describe my experience with minix community. Recently I made a small code contribution to minix3 (committed on 15 Oct 2012), it is available here, as some of fellow ILUGC (Linux User’s group) members were interested to know about my experience I was requested to write a blog post about it. As this is my first code contribution to an open source project I think it will be helpful / interesting to people who want to start code contribution.

My plans

I wanted to contribute to some open source project, I was searching for some place to contribute. My initial thought was to contribute to Linux kernel in form of device drivers as contributing to core kernel needs a good knowledge and time. All the devices that I had drivers for Linux (I am lucky and unlucky :P). I was not able to find device that had documentation but no driver (very rare possibility). So I thought of working for some other project. I wanted to limit myself to OS, drivers, graphics or mathematics related projects.

Initial Stages

I came across minix project. Most of them who had taken a OS course or know Linux history must be aware of minix. At that time minix was for students and contribution to it was not much encouraged (it was intended for teaching purpose). But as of minix 3 and later the license changed to BSD and people are encouraged to contribute to it (I am not aware of the status of minix 2 or other versions). I read the wishlist, roadmap described in the minix3 website. I also downloaded, installed minix3 in a VM in my machine. So far things went well. I chose to work on FAT file system driver (or in minix parlance a file system server) as I did not need any special device and I can test it from within a VM. I started working on FAT 16 and FAT 32 file system driver implementation for minix 3. I wanted to write from scratch so I did not try to port code from other projects (I was able to find some fat16/32 BSD licensed implementation but I did not try to port them intentionally) as I wanted to learn as much as possible.

Hard road ahead

As I have made a choice on the work I started working. I tried to go through many online documentation on FAT 16/32 file systems. As I was new to it I read from many sources and I reached a state where there was conflict between sources and I was not sure which source is correct. Some authentic and correct source were covered by NDA or some sort of license which does not permit me to write a BSD licensed code using those. I did not go through other fat implementation (like linux’s or *BSD’s as I want to do it fully myself). At this stage I had done parsing BIOS parameter block but I did not spend much time on designing or architecturing the code – the code obviously became ugly (not well written).

Jump from FAT implementation

At this point I did not have a stern documentation, not well designed code so I stopped here. I paused I did not actually stop. My mind said “make smaller contributions while working on fat implementation slowly”. I followed my mind. I used to be present in #minix IRC channel as much as possible. I started to speak with people in #minix. I came to know pikpik was working on “removing usage of 64 bit functions” and it seemed I could work on that (pikpik actually had a lot of work done and it was available in his branch and not merged). It seemed doable for me and I plunged into working it. Got the diff’s from pikpik and started working from there.

Moving forward in “Removing usage of 64bit functions”

I will describe what the phrase “removing usage of 64bit functions” mean when required. I just checked if the patches are correct – by manually going through the changes (not by testing the changes). I wanted to commit the changes module by module. I chose to work on the changes made by pikpik in top utility (top.c file). Found some bugs and fixed them. As soon as I finished this I went to the minix mailing list and fired a mail requesting to merge the changes along with a link to the change (it is a github link and github allows inline commenting).

Many people in minix group took great effort to review the code that I wrote and I got valuable comments. After some time I got a reply from Saturn (this is his IRC nick) that the changes I have made can be done by some simple scripts and does not do the real required change. Yes I did not go through the code and I did not understand that just changed things mechanically. The code required real change which I missed. I would really thank him as he pinpointed out that I have not done worthy code (a python or perl script could actually do what I had done at that time). Then I decided to plunge into the code to make necessary change as suggested by him.

I would like to explain the phrase “removing usage of 64bit functions” and what the “real change” phrase seen in previous paragraph meant. In Minix to do addition, subtraction, multiplication, division, comparison etc of 64bit data type (uint64_t or unsigned long) the corresponding functions were called (not operators). This was due to old compiler which did not support these (kind of legacy stuff). Now the compiler has been changed (minix uses gcc and llvm) but the code remains the same in many places. I planned to replace the functions with operators (really a mechanical job). In top utility (top.c file) there was a trick applied. The 64bit values were converted to 32bit values using a shift, the resultant 32bit values and operators are used. It worked but the code does not look cool, Saturn wanted to remove this trick. Removal of the trick(64bit to 32bit conversion using a shift and working on it) is what the phrase “real change” meant.

Plunge into the “Real change”

I started to work on it. I went through the code flow and understood what I should do. Made the necessary changes in code (implementing was very simple once I got the idea). Requested for merge again through mailing list. This time I got a small amount of review comments (from Saturn again) and it was code readability change (no change in functionality or other major code change). I did them and got back again with new changes.

The code change was acknowledged by Saturn and he said the code is in a good shape and can be merged into minix tree :). After a day I guess there was another mail saying that the code is merged and is available in minix mainline tree. I was very happy to see my code change merged 🙂 :).

Tips for newbies who want to contribute to open source project especially minix”

1. Be available in the projects IRC channel and subscribe to mailing lists.

2. Ask the doubts that you have. Even if it seems silly ask it, people will be there to reply or direct you to correct place.

3. Reviews and comments are for improving code quality and making you understand how good code is made. Don’t take it personal or thing them as negative.

4. Ask for TODO tasks, wish list or road map. But before that explain them what you know and what is your area of expertise or interest. In companies people will be assigned tasks but in case of open source work people will take work that suits them (what they like) and work on it. So don’t ask someone to assign tasks to you.

5. Most of the people in IRC are great. Especially in #minix most were responsive, encouraging – pikpik, cphuntington97 and others (whom I could have missed or forgot in this late hours) were very encouraging and supportive.

If the above basic steps are followed things will go great :). All the best for your contribution to open source projects.


1. I will resume my work on fat file system implementation soon while carrying out other tasks.

2. I have written what came through my mind, it may not be well structured. If there is a need to re-structure it or modify some lines please let me know through comments.

3. Please let me know about your thoughts. Ask questions if there are any in comments and I will be glad to explain.


5 thoughts on “My experiences in contributing to minix 3

  1. It is great to hear you had a positive experience with your first contribution to Minix! And very good of you to document your experience with such a positive, detailed blog post, as it encourages others, as you said, and that in turn is great for the Minix project. So thank you for taking the trouble! And please stay around as a Minix contributor 🙂

  2. Good work!
    I agree with Ben Gras, and I note that the value of the message is that in this way a lot of people walking. Description of the problems and analysis of the events are very valuable. I think, from here one can understand the general direction.
    It is necessary to subscribe to #minix in IRC …

    Studied the post of 3 days, added to the dictionary more than 200 words. My English is much worse your 🙂
    I can turn to you for advice in the future?

  3. Hi prasannakumartsm,

    Your post is very valuable.
    In fact I like to contribute to minix 3 too, so I look for one simple task and found the change on 64 bits operations. I do some grep on the source tree and then I do some search on the groups in order to understand how to share the source code changes and how the coordination of the source code works. At this stage I found your post and this blog !!!
    So I like to say you thanks for share your experience with the rest of us.
    Are you finished with the changes ?
    May be I can contribute with the other beggineer tasks
    I will ask on the group
    Be well

    1. Hi Gus, Glad my post helps you :). I have not yet done with changes. There are lot of files using those functions. I am doing things slowly. As I have not got used to git scm I am having some trouble in doing merge, rebase etc :(. Yet to learn a lot in git.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s