mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Noud Aldenhoven" <jwaixs@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to learn Linux Kernel Programming
Date: Wed, 22 Aug 2007 02:48:16 +0200	[thread overview]
Message-ID: <9a8748490708211748v4c1aacbak3a44f893d08381ae@mail.gmail.com> (raw)
In-Reply-To: <cb63d1e10708211229n18cc154ep43912a671ca1bfee@mail.gmail.com>

On 21/08/07, Noud Aldenhoven <jwaixs@gmail.com> wrote:
> Hello Kernel Develop mailing list,
>
...
>
> I'm a simple Math/Computer Science student and would like to learn
> more about linux and it's kernel.
> To be more precise, I'd to learn how to program in the linux kernel
> and maybe become a developer,
> if everything goes fine.
> But where do I start?

Start by reading Documentation/HOWTO from a recent copy of the kernel source.


> Almost all information I found on the Internet
> if from before 2005

There's lots of good kernel related material to be found online. See
for example :

http://kernelnewbies.org/
http://janitor.kernelnewbies.org/
http://lwn.net/Kernel/LDD3/
http://lwn.net/Kernel/
http://kerneltrap.org/
http://kerneltraffic.org/


> and I think that
> means it's out-of-date.

That's not always true.


> Are there up-to-date documentations that are
> use full to read and explain how
> the kernel is build. (for example, is /usr/src/linux/Documentation a
> use full dir?)

Yes it is useful.  Not everything in there is 100% up-to-date, but
there is still a *LOT* of useful documentation to be found there.


> An other question I'd like to ask is how and where did you start? I'd
> like to know how you manage to became
> linux kernel developers.
>
Most people start out fixing small bugs, cleanups etc or by
implementing some small feature or driver that they need. There's no
fixed way.


-- 
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:[~2007-08-22  0:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cb63d1e10708211228u383240a2l4af811f72b8858c0@mail.gmail.com>
2007-08-21 19:29 ` Noud Aldenhoven
2007-08-21 19:53   ` Rik van Riel
2007-08-22  0:48   ` Jesper Juhl [this message]
2007-08-22  3:15   ` Glauber de Oliveira Costa
     [not found]     ` <cb63d1e10708212346l746111dcic584b4bb5fe461fc@mail.gmail.com>
2007-08-22  6:47       ` Noud Aldenhoven
2007-08-22  9:07         ` Nicolas Vigier
2007-08-22 10:06         ` Jesper Juhl
2007-08-22 10:42         ` Bernd Petrovitsch

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=9a8748490708211748v4c1aacbak3a44f893d08381ae@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=jwaixs@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®