discuss

gvim

Linux has plenty of books dedicated to annotate its source code, but unforunately, BSD, we do not have such a book detailed in code level.
Also, BSD has less documents to describe the iinfrastructures behand what we could see. It seems that they, the *BSD makers, do excellent communication with the machine but not human.

So:
How can we study BSD kernel well?
How do you read the software codes which not only the operating system but also the up level applications/frameware?
How to make the relativity which introduced by individual modules together
How to work through the vast codes? I usually had a headache.
How to keep function-calls tree as more you need?

Any questions and answers are welcome.
Let's have a talk.

[ 本帖最后由 gvim 于 2006-4-29 10:22 编辑 ]

雨丝风片

原帖由 gvim 于 2006-4-29 02:57 发表
Linux has plenty of books dedicated to annotate its source code, but unforunately, BSD, we do not have such a book detailed in code level.
Also, BSD have less documents to describe the iinfrastruc ...

半夜三更说的梦话都是鸟语嘀。。。
这些问题非常值得讨论，鉴定完毕。楼下继续。。。

congli

原帖由 雨丝风片 于 2006-4-29 07:58 发表


半夜三更说的梦话都是鸟语嘀。。。
这些问题非常值得讨论，鉴定完毕。楼下继续。。。

这些鸟语看得挺辛苦,楼下继续...

剑心通明

原帖由 congli 于 2006-4-29 08:02 发表

这些鸟语看得挺辛苦,楼下继续...

服了你们了，别打击嘛，虽然俺也基本上同意你们的观点:wink:

雨丝风片

原帖由 gvim 于 2006-4-29 02:57 发表
How can we study BSD kernel well?
How do you read the software codes which not only the operating system but also the up level applications/frameware?
How to make the relativity which introduced by individual modules together
How to work through the vast codes? I usually had a headache.
How to keep function-calls tree as more you need?
...

1、先读《设计与实现》，后动手，内核是要折腾的，用官方的话说，那叫hack。。。
2、以线带面。
3、模块接口是个纲，纲举目张。
4、常备头痛药，读码最需要。
5、纸上画、阅读工具里生成、调试内核时show。。。

gvim

出差刚到家，洗洗澡居然异常亢奋。

我觉得我遇到的问题在于:虽然模块的描述比较多，但模块之间的支撑框架描述比较少。很厌恶。
而且这些文章，多半有些过时！对着代码分析半天才能得出新的结论，非常令人沮丧。甚至如风雨所言man page都有old，我也不止碰到一两次。
代码里的注释十分的english，相当的随意。虽然都是英语，但是不同人的语言表达差异十分大。往往一段注释要看7，8遍才能理解到他什么意思。

雨丝风片

首先还是得把理论基础打好，看代码之前脑子里得已经有一个大致的图像才行，然后再用
这个图像去套代码，先不用关心代码细节，大致浏览一下，分析出代码的主要脉络，修正
之前形成的理论轮廓，然后再继续深入，逐步细化脑子里的图像。

gvim

是这样的。代码部分捡重点分析，其他的知道理论、知晓机理。
呵呵，我们的分析不知道什么时候才能烧有起色。

balabalacha

学习！