> as opposed to a majority of people who talk and not code anything?
Good point.
I was wondering what to do next, once/if I can finish fixing a wi
driver issue...
Let me raise one question... There are quite a few books written about how
certain things work on a kernel level, but they're for other operating systems.
If we had such documentation, even if it isn't kept up-to-date, it would be a
start point. As I stated in an earlier message, OpenBSD code is very, very
readable. It could be used in lots of college classes around the world. A
book could provide an additional way to fund the project. Obviously, it is not
an easy task, particularly from the commercial side. Deals would have to
be made and they tend to be more attractive to the publisher side....
| debian developer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| Linus Torvalds | Re: Long delay in resume from RAM (Was Re: [patch 00/69] -stablereview) |
| Parag Warudkar | BUG: soft lockup - CPU#1 stuck for 15s! [swapper:0] |
git: | |
| Andi Kleen | [PATCH RFC] [4/9] modpost: Fix format string warnings |
| Rick Jones | Re: Network latency regressions from 2.6.22 to 2.6.29 |
| Antonio Almeida | HTB accuracy for high speed |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
