On 10/31/07, Marcus Andree  wrote:

quoted text
> 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....

for one thing, it would always be out of date.
and the thing people need to learn is not specifics, but principles.

not so much priniciples of operating system development (though that

is important), but openbsd principles.
take pf.  every release it does more, but the principle is that it

should be as simple as possible.  this principle is more important

than any discussion of binary trees vs hash tables vs cryptographic

checksums or whatnot.