From: Steven Rostedt <rostedt@goodmis.org>
To: ed <ed@ednevitible.co.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Book recommendations
Date: Fri, 23 Dec 2005 19:11:50 -0500 [thread overview]
Message-ID: <1135383110.5774.12.camel@localhost.localdomain> (raw)
In-Reply-To: <20051223231115.5f678e5a@workstation>
On Fri, 2005-12-23 at 23:11 +0000, ed 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.
Previously, I recommended three books:
http://www.kerneltraffic.org/kernel-traffic/kt20050605_312.html#8
and Greg KH wrote up a nice howto:
http://www.kernel.org/git/?p=linux/kernel/git/gregkh/patches.git;a=blob;f=HOWTO
-- Steve
next prev parent reply other threads:[~2005-12-24 0:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 23:11 Book recommendations ed
2005-12-23 23:27 ` Michal Piotrowski
2005-12-24 0:11 ` Steven Rostedt [this message]
2005-12-24 10:33 ` Pekka Enberg
2005-12-24 12:38 ` ed
2005-12-24 12:41 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2002-11-13 12:10 Book Recommendations [ Jason ]
2002-11-12 19:45 Paul Kraus
2002-11-12 21:17 ` Ray Olszewski
2002-11-12 22:51 ` Elias Athanasopoulos
2002-11-13 10:27 ` dashielljt
2002-11-13 14:11 ` Joshua Lee
2002-11-12 21:34 ` Elias Athanasopoulos
2002-11-13 14:01 ` Joshua Lee
2002-11-12 6:24 [ Jason ]
2002-11-13 22:01 ` Elias Athanasopoulos
2002-11-14 9:51 ` dashielljt
2002-11-14 20:32 ` Elias Athanasopoulos
2002-11-14 19:27 ` Ray Olszewski
2002-11-15 11:25 ` Elias Athanasopoulos
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=1135383110.5774.12.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=ed@ednevitible.co.uk \
--cc=gregkh@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.