From: Daniel Drake <dsd@reactivated.net>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Developing Kernel Code newbie
Date: Mon, 15 Sep 2003 10:49:42 +0100 [thread overview]
Message-ID: <3F658B36.2010503@reactivated.net> (raw)
In-Reply-To: <3F6579CD.5010609@cyberone.com.au>
I'm in a similar situation here.. a C/C++ beginner, very keen to work on
the Linux kernel.
Those two books you mentioned, the latest editions cover the 2.4 series
kernel. Would reading these still be useful for working on the 2.6 (and
onwards) kernels?
Thanks.
Nick Piggin wrote:
>
>
> Amir Hermelin wrote:
>
>> Hi,
>> I've recently started development on the Linux Kernel, and wondered if
>> there's any kernel-dev FAQ/Howto/online courses/etc to help me get
>> started
>> with debugging techniques. Any help would be greatly appreciated.
>>
>
> Understanding the Linux Kernel and Linux Device Drivers (free online I
> think) are 2 good books to start with. Also www.kernelnewbies.org.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-09-15 9:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 7:59 Developing Kernel Code newbie Amir Hermelin
2003-09-15 8:35 ` Nick Piggin
2003-09-15 9:49 ` Daniel Drake [this message]
2003-09-15 9:52 ` Nick Piggin
2003-09-15 15:11 ` Daniel Drake
2003-09-15 13:55 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-09-15 7:57 Amir Hermelin
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=3F658B36.2010503@reactivated.net \
--to=dsd@reactivated.net \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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