[lkml]   [2001]   [Oct]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: In great need
On October 25, 2001 06:34 pm, Jonathan Corbet wrote:
> > Were should I start.
> is intended to be a starting place for kernel hackers.
> May I also humbly suggest _Linux_Device_Drivers_? It's online at
> But, of course, you'll want to buy a copy at the bookstore of your choice
> as well :)

Yes, that's where I started. Being somewhat impatient, I just flipped to
chapter two, which has a 4 line example of a kernel module which I'll
paraphrase here:

#define MODULE
#include <linux/module.h>

int init_module(void) { printk("Hello kernel!\n"); return 0; }
void cleanup_module(void) { printk("Goodbye kernel!\n"); }

Then I did (more or less):

cc -c hello.c -I/usr/src/2.4.12/include
insmod hello.o
rmmod hello

So my first kernel hack took about 5 minutes, with the help of this book.
Note: some of that 5 minutes was spent figuring out that kernel messages
don't get printed to the console if you're running X, hence the dmesg's.

You'll have to update the example in the book - simply doing "cc -c hello.c"
works only when the /usr/include/version.h happens to match your running
kernel, which isn't very likely.[1]

The big advantage of starting with module programming is, you don't
necessarily have to understand the entire kernel to get started - the
interfaces available to modules tend to be easier to understand and work with
than the other, often subtle and sparsely documented interfaces used
internally by the kernel itself.

And yes, I do have to go out and get the 2nd edition of LDD, co-starring you

[1] Because /usr/include/linux is no longer allowed to symlink to

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:10    [W:0.076 / U:0.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site