From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
To: ed <ed@ednevitible.co.uk>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Book recommendations
Date: Sat, 24 Dec 2005 00:27:21 +0100 [thread overview]
Message-ID: <6bffcb0e0512231527h5ca8b3caq@mail.gmail.com> (raw)
In-Reply-To: <20051223231115.5f678e5a@workstation>
Hi,
On 24/12/05, ed <ed@ednevitible.co.uk> wrote:
> Hello,
>
> I am looking to get involved in kernel development, maybe start first
> with looking at very minor bugs effecting my local system etc.
>
> First I would like some advice on choosing reading material, has anyone
> any good advice? I have previously read Unix Internals - Pate, but this
> is not deep enough and closer to SCO than linux.
Linux Kernel Development, 2ed
http://rlove.org/kernel_book/
Linux Device Drivers 3
http://lwn.net/Kernel/LDD3/
http://www.kernelnewbies.org/
Regards,
Michal Piotrowski
next prev parent reply other threads:[~2005-12-23 23:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 23:11 Book recommendations ed
2005-12-23 23:27 ` Michal Piotrowski [this message]
2005-12-24 0:11 ` Steven Rostedt
2005-12-24 10:33 ` Pekka Enberg
2005-12-24 12:38 ` ed
2005-12-24 12:41 ` Steven Rostedt
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=6bffcb0e0512231527h5ca8b3caq@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=ed@ednevitible.co.uk \
--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