Well I am reading the paper book when I’m not in front of a computer. There’s no problem on this when I’m reading the principle chapters. However, it is really not easy to read the code on a paper if you are too customized to the facilities of a computer, like tags search and syntax highlight. So I’ve decide to go on with the principle chapters and leave the code reading later. This may also benefit cause I’ll have a more wide view of the OS when I read the code.
And here’s some of my thought about how I will read and document the code:
The best way I can think of is to use Doxygen and Doxymacs. And I’m learning mind map and FreeMind, I’m thinking using freemind to get the scheleton of the code. One question now is that I don’t know how to point to a freemind node from the doxygen document.
And I think I can use version control systems to manage my update on the using of doxygen. Say the trunk for keeping up with the official code, a document branch for doxygen changes, and a sandbox branch for change it here and there to build and test.
I’m not sure if the license allow me to publish my doxygen and freemind output. Need to check this later, if I can make it, ofcause 
Tags: minix, doxygen, freemind, programming
Post a Comment
You could use <code type="name"> to get your code colorized