From: xerofoify@gmail.com (nick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How do _you_ read the linux source?
Date: Mon, 20 Apr 2015 08:47:38 -0400 [thread overview]
Message-ID: <5534F56A.1020107@gmail.com> (raw)
In-Reply-To: <CAG9Fz+tdd5Z=FUMnJtD0uvJvbMKdsK7ar+9K_YLAvv91Oft6Jg@mail.gmail.com>
On 2015-04-20 01:45 AM, Christoffer Holmstedt wrote:
> 2015-04-20 5:11 GMT+02:00 nick <xerofoify@gmail.com>:
>> There were a few things I did when starting to learn the kernel
>> 1. Read Robert Love's Linux Kernel Development, I don't care how much you think
>> you known about the kernel read and trace the actual kernel code with this book!!
>> 2.Read a book on device drivers and the Linux networking stack, I
>> read Linux networking internals for this
>
> Thank you Nick, I'm just getting started with linux kernel development
> and have been looking around for books both more general and specific
> to networking. One thing in common several books I've found have is
> that they are based on the 2.6 version of the kernel (or older). Some
> parts have changed but are entire chapters in the above mentioned
> books too old to make sense when working on version linux kernel 4.1
> and beyond?
>
What you need to do is look at the source code and see what has changed this writing
of the book. This is what I do when reading kernel programming books or documentation.
Further more around way is to read the logs of the networking mailing lists for the
kernel to see what has changed recently.
Nick
next prev parent reply other threads:[~2015-04-20 12:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 1:57 How do _you_ read the linux source? r00nk at simplecpu.com
2015-04-20 3:11 ` nick
2015-04-20 5:45 ` Christoffer Holmstedt
2015-04-20 12:47 ` nick [this message]
2015-04-20 15:45 ` Valdis.Kletnieks at vt.edu
2015-04-20 12:04 ` Robert P. J. Day
2015-04-21 0:46 ` r00nk at simplecpu.com
2015-04-21 16:45 ` John de la Garza
2015-04-21 1:08 ` Miles Fidelman
2015-04-20 14:51 ` Greg KH
2015-04-21 0:16 ` Milton Krutt
2015-04-21 0:38 ` Ruben Safir
2015-04-20 16:32 ` Jeff Haran
2015-04-20 16:43 ` Ruben Safir
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=5534F56A.1020107@gmail.com \
--to=xerofoify@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).