Re: [Kernelbook-feedback] suggestions for the book

[Gary L. M. <ga...@ca...>]

>>>>> "p" == pvlad  <pv...@bi...> writes:

    p> what type of technical resources needed how does a project plan
    p> look for such a project (time for design, implementation,
    p> testing) -- just approximate estimates that come from one of
    p> the implementations with average complexity.  

Yes, this is probably out of the scope of this book, although the
chapter on tools could add a little of what you want.  I stuck with
only listing those tools essential to actually working on the kernel
rather than those project management things that are common to any
large project.

    p> As far as the 'reference' section is concerned -- I would agree
    p> that it is better to have separate from the main book.  

I tend to agree, but the kernel-doc project is integrating them. 

I'd like them as two different (cross-ref'ed) books as I would use
both differently --- with other API books, I find I am always picking
it up only to read the API section whereas, as you say, a beach is a
good place for a tutorial (I live on a beach)

I suppose I can take the paperback and just split the spine of it ;)

-- 
Gary Lawrence Murphy <ga...@te...> TeleDynamics Communications Inc
Business Innovations Through Open Source Systems: http://www.teledyn.com
Free Internet for a Free O/S? - http://www.teledyn.com/products/FreeWWW/
"Computers are useless.  They can only give you answers."(Pablo Picasso)