my way is to grasp the call graph and data structures at first. and if u can know the purpose of one function, u need not know every detail about it. once u go through whole flow once, then u can go deeper.
and for some code has algorithm, u had better know that algorithm first. instead of reading code to know the algoritm.
for code implement protocol. for example a scsi protocol. u had better have a scsi command reference at hand.
most of the time, i skip the asm code and machine dependent code, since i do not go that deeper. i read code because i need do my research. if u have no such requirement, try to find one.
u should not touch u current kernel source code and kernel image. u need use another copy of kernel source and modify in that.
and if possible. use user mode linux is a good choice.
may be I can ask Dragonfly something about 'user mode linux'
I don't know what it is,since I never heard it.
Can you introduce it to me?
Is it something you can compile the kernel in time and use it to check that immediately?
If so,I would install one.
The next term I have a course called practice to operation system,
and it will do me a great help!
i am very interested in usr-mode-linux,i have done some experiment according to the web site(use-mode),but all are fail,nothing happened.
so,Dragronfly,would you please talk something about it?
thanks very much
I have some exp on Windows user mode debug. It is not easy because there is no code to check, only depend on the asm. Debugging the kernel also is suck. Need to two computers.
However, I am a new fresh on Linux. I even don't know how to debug user mode in Linux. This forum is the beginning for me. I wish to learn some and quickly master Linux.