public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: regatta <regatta@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to be a kernel developer ?
Date: Tue, 19 Jul 2005 03:11:08 +0200	[thread overview]
Message-ID: <9a87484905071818116f7cb0de@mail.gmail.com> (raw)
In-Reply-To: <5a3ed56505071807357fc419e7@mail.gmail.com>

On 7/18/05, regatta <regatta@gmail.com> wrote:
> Hi
> 
> I want to join the Kernel community and help in developing Linux
> kernel, I'm good in C,Perl and  not that good in C++
> 
The kernel is written in (mainly) C and (a little bit of) asm, no C++ in there.

> is there any How-To page in how to help or how to join ? since I want
> to start in basic things
> 
A few things you should do : 

- Take a look in the Documentation/ directory in the kernel source,
you'll find lots of valuable information there.

- Go check out http://kernelnewbies.org/

- You may also find this online source browser useful (I know I do)
http://lxr.linux.no/

- Keep a link to a LKML archive in your bookmarks and search the
archives for answers whenever you have a question - chances are good
that whatever you want to ask has been asked before and answered in
depth on the list, so it'll be in the archives. Here's one LKML
archive you can use, it goes back a few years :
http://www.ussg.iu.edu/hypermail/linux/kernel/

- Subscribe to LKML and start reading the some of the threads. A lot
can be learned by reading the bugreports and solutions that pop up on
the list, there are also often discussions on ideas, implementation
details, debugging etc etc that can be valuable. So join the list and
start listening :)  ohh, and do read the lists FAQ at
http://www.tux.org/lkml/

- You may also want to join the Linux Kernel Janitors
http://janitor.kernelnewbies.org/ - they have a mailing list and a
nice TODO list of things that need doing - good place to pick a small
starting project from.

- You should also, most likely, invest in a few books on the kernel
and read them. I'd recommend these two as good ones to start with :
"Linux Kernel Development (2nd Edition), by Robert Love" and "Linux
Device Drivers (Third Edition), by Jonathan Corbet, Alessandro Rubini,
and Greg Kroah-Hartman".

- And most important of all, start reading the kernel source, and play
with the kernel source. Reading the source, making some changes and
then testing them and learning from the mistakes you make is a great
way to learn.


-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  parent reply	other threads:[~2005-07-19  1:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-18 14:35 how to be a kernel developer ? regatta
2005-07-18 14:43 ` Alejandro Bonilla
2005-07-18 16:22   ` Andrew Ruder
2005-07-19  1:11 ` Jesper Juhl [this message]
2005-07-19  1:24   ` Jesper Juhl
2005-07-19 21:53   ` how to be (SAFE) " Brian O'Mahoney
2005-07-19 23:02     ` Jan Blunck
2005-07-20  0:25     ` Jesper Juhl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9a87484905071818116f7cb0de@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regatta@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox