Re: suggestions for new kernel hacking-HOWTO

[Pragnesh Sampat <pss@sampatonline.com>]

> - Key Kernel Concepts
> 	(placing these in a good order is important)
>         - virtual memory/memory management
>         - virtual file system/IO management
>         - process/scheduling
>         - contexts/interrupts/exceptions
>         - system calls/signals/IPC
>         - boot sequence

> - Kernel source tour
>         What goes where in the source tree
> 

I am not sure if these two sections are suitable in this howto.  It
seems pretty ambitious, since they can get very large and the
books/resources sections can take care of this.  The book "Linux
Device Drivers" by Rubini and Corbet has got a section on source tour.

> - How do I... ?
>         - Print messages to kernel logs
>         - create a new module
>         - Add a system call
>         - write ioctls
>         - Add a /proc entry
>         - Write a driver for a new device
>         - Add an option to the kernel configuation
> 
> - Kernel Debugging
>         - A word on debugging
>         - Different approaches
>                 - local running kernel
>                 - UML
>         - two box debugging (I have already write a sort of mini HOWTO
> on this, which can be found at
> http://www.kernelhacking.org/docs/2boxdebugging.txt)
>         	- Setting up
>                 	- hardware
>                 	- software
>         	- Preparing the source
>         	- Example debugging session
>         	- Troublshooting
> 

Kernel Debugging can probably go ahead of the "How do I...?" section,
since in practice you probably need some variant of the the setup you
have described before you start, unless you are just trying out a
trivial module.

In fact, if the concepts section is not there, the whole document
seems to have the structure of how to do something, with sub sections
of varying length (after all, it is hacking HOWTO).

-Pragnesh