Wrong attempt IMHO. Trying to write a centralised document for the linux
kernel, even if maintained by a staff of people, will definitely fail.
I´ve looked into several books about the kernel, most of them deal with
2.0 or even 1.2 kernels. Outdated by far. Those that deal with 2.1 are
mostly uncomplete.
Additionally, someone, even with decent knowledge of common OS design
will spend lots of time in understanding linux´ structures and
mechanisms and for that time be unable to catch up with the "wheel".
So I suggest that who writes the code, documents it. Some of you now
might claim that this will slow down development. Agreed. But the
project "linux" has grown to an extent that is not overseeable for a
person looking from "outside", may he be as skilled a programmer as can
be. Good documentation will lead to higher quality of kernel code, it's
definitely worth the effort. Already there are many examples of bad
kernel code that's due to misunderstood concepts. Just mentioning the
dev->tbusy thingy.
Gruss,
Matthias
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/