Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Thanks, Actually I am new to module development. I just wanted to confirm that by including "Kernel Hacking" am I including all debug facilities or there are something more somewhere. I don't know any thing about debug tools requirement, but I want to make sure that I don't have to recompile it again for another debug tool to work. Commented Jun 25, 2011 at 12:17
  • If you are doing kernel debug work get used to recompiling the kernel! The best thing to do would be to automate the process so that any changes require as little effort from you as possible. Of course modules can be compiled without rebuilding the whole kernel, but you'll find you'll want to do this anyway now and then. Reasons come up. I can build a new kernel in a few seconds with a couple keys using script that does everything from finding and downloading the latest version, matching my current config, allowing me to make any config changes, compiling, installing, editing my boot loader. Commented Jun 25, 2011 at 12:24