From: Nick Piggin <piggin@cyberone.com.au>
To: Daniel Drake <dsd@reactivated.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Developing Kernel Code newbie
Date: Mon, 15 Sep 2003 19:52:49 +1000 [thread overview]
Message-ID: <3F658BF1.6070703@cyberone.com.au> (raw)
In-Reply-To: <3F658B36.2010503@reactivated.net>
Daniel Drake wrote:
> 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?
Yes.
If you are a _programming_ beginner, you're setting your sights a too high
and will probably get frustrated.
next prev parent reply other threads:[~2003-09-15 9:53 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
2003-09-15 9:52 ` Nick Piggin [this message]
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=3F658BF1.6070703@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=dsd@reactivated.net \
--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