On Mon, Nov 26, 2001 at 03:49:16PM +0000, Andrew Ebling wrote: > I'm also starting to feel that my document will be a bit too big for a > howto by the time it is complete. Perhaps "guide" status would be more > appropriate. :nods > List: do you guys think it would be better to have an integrated, > formal, guide to replace the aging/disparate KHG (with a dedicated > chapter on modules)? Or would it be better to keep the module > programming guide separate? I would tend towards keeping them separate but work together (if you see what I mean). Your guide has lots of info on basic terms and systems, and how they operate. In my mind, the MPG should focus on being a useful guide for someone who wants to write a kernel module. In the MPG, API and the usage of that API is more important. > I think it would be really good to have a centralised, comprenhensive, > up to date document on all aspects of kernel programming that is a good > primer for newbies and an authoritative reference for more seasoned > hacker. yes ... john -- "By the way, it's not binaries, it's Perl code. Sometimes they look confusingly similar." - Pavel Roskin -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ IRC Channel: irc.openprojects.net / #kernelnewbies Web Page: http://www.kernelnewbies.org/
