On Tuesday 11 October 2005 17:02, Randy McMurchy wrote: > Richard A Downing wrote these words on 10/11/05 15:52 CST: > > Take tongue out of cheek. We are FAR better at keeping our > > documentation up to date than the Kernel Developers who would rather > > introduce a 'really neat bit of new code' than document the bloody > > important stuff they wrote last year. > > Simply for the sake of discussion, let me pose a question. > > Certainly there is limited amount of time the kernel dev's have to > spend on the project. > > Would you rather that time be spent in documenting their work, or > developing new code and fixing bugs in old code? > > In a perfect world, or when you work for an employer, you must do > both. But in an open-source environment, this might not be feasible. > > Just a thought. > > -- > Randy
There are actually some books available on the linux source code, which you can buy; I have no idea if they're good or not. They fulfill the predictable open source pattern: You get the code for free, but pay for elements like support or documentation - things that hackers don't want to do for fun. Books such as _The Linux® Kernel Primer: A Top-Down Approach for x86 and PowerPC Architectures_ (ISBN 0-13-118163-7) which is 648 pages covering kernel 2.6, or _Understanding the Linux Kernel, 2nd Edition_ (ISBN 0-596-00213-0) which is 784 pages on kernel 2.4. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
