public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Luca <kronos@kronoz.cjb.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] HOWTO do Linux kernel development
Date: Tue, 15 Nov 2005 12:56:18 -0800	[thread overview]
Message-ID: <20051115205618.GA11205@suse.de> (raw)
In-Reply-To: <20051115201051.GA13473@dreamland.darkstar.lan>

On Tue, Nov 15, 2005 at 09:10:51PM +0100, Luca wrote:
> Greg KH <gregkh@suse.de> ha scritto:
> > Intro
> > -----
> [...]
> > Though they
> > are not a good substitute for a solid C education and/or years of
> > experience, the following books are good, if anything for reference:
> > 
> > "The C Programming Language" by Kernighan and Ritchie [Prentice Hall]
> > "Practical C Programming" by Steve Oualline [O'Reilly]
> > "Programming the 80386" by Crawford and Gelsinger [Sybek]
> > "UNIX Systems for Modern Architectures" by Curt Schimmel [Addison Wesley]
> 
> Hi Greg,
> you may want to add:
> 
> "Linux Kernel Development, 2nd ed." by Robert Love [Novell Press]
> and
> "Linux Device Drivers, 3rd ed." by J. Corbet, A. Rubini and G. Kroah-Hartman [O'Reilly]
> 
> IMHO the first one is a must-have for beginners who want to have an
> overall picture of the kernel and LDD is very helpful when you start doing
> some real work :)

Those books are good, but this section is just for where to get the
basics of C and Unix.  The file Documentation/kernel-docs.txt should
have a pointer to these two books, and this HOWTO does point to that
file.

thanks,

greg k-h

  parent reply	other threads:[~2005-11-15 21:14 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 22:07 [RFC] HOWTO do Linux kernel development Greg KH
2005-11-14 22:10 ` Greg KH
2005-11-14 22:43   ` [RFC] [HUMOR] " Jeffrey V. Merkey
2005-11-15  0:18   ` [RFC] " Kalin KOZHUHAROV
2005-11-15  0:32     ` Randy.Dunlap
2005-11-15  4:58     ` Greg KH
2005-11-15  8:37       ` Paolo Ciarrocchi
2005-11-15 19:04         ` Greg KH
2005-11-15  0:32   ` Josh Boyer
2005-11-15  1:25     ` Paul Jackson
2005-11-15  1:31       ` Randy.Dunlap
2005-11-15  2:16       ` Josh Boyer
2005-11-15  2:42         ` Paul Jackson
2005-11-15  2:52           ` Josh Boyer
2005-11-15  3:01             ` Paul Jackson
2005-11-15  4:48               ` Greg KH
2005-11-15  4:47             ` Greg KH
2005-11-15  1:08 ` Coywolf Qi Hunt
2005-11-15  4:38   ` Greg KH
2005-11-15  5:51     ` Coywolf Qi Hunt
2005-11-15  5:52       ` Greg KH
2005-11-15  6:31         ` Coywolf Qi Hunt
2005-11-17 13:54         ` Pavel Machek
2005-11-15 14:42 ` Andi Kleen
2005-11-15 17:33   ` Greg KH
2005-11-16  8:12     ` Michael Kerrisk
2005-11-17  6:56       ` Greg KH
2005-11-17 12:12         ` Michael Kerrisk
2005-11-15 20:10 ` Luca
2005-11-15 20:13   ` Josh Boyer
2005-11-15 20:56   ` Greg KH [this message]
2005-11-16  4:38     ` Randy.Dunlap
2005-11-15 22:20   ` sitexec
  -- strict thread matches above, loose matches on Subject: below --
2005-11-16 12:15 linux

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=20051115205618.GA11205@suse.de \
    --to=gregkh@suse.de \
    --cc=kronos@kronoz.cjb.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