kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How do _you_ read the linux source?
Date: Mon, 20 Apr 2015 11:45:26 -0400	[thread overview]
Message-ID: <6428.1429544726@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 20 Apr 2015 07:45:37 +0200." <CAG9Fz+tdd5Z=FUMnJtD0uvJvbMKdsK7ar+9K_YLAvv91Oft6Jg@mail.gmail.com>

On Mon, 20 Apr 2015 07:45:37 +0200, Christoffer Holmstedt said:

> 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?

The details have changed.  The basic concepts haven't.  In fact, the *basic*
concepts change so slowly that reading Bach's book on the SYSV kernel or
McKusic & Liefler on the BSD kernel will teach you a lot.

In fact, I'll go out on a limb and say that reading how *other* systems have
solved the same issues is a Good Thing. Knowing just "Linux solved it this way"
is one thing, but knowing "Linux solved it this way, but BSD took a different
approach because X, and IBM's VM/SP did Y instead to avoid the issue entirely"
is a whole different level of understanding.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150420/fed99190/attachment.bin 

  parent reply	other threads:[~2015-04-20 15:45 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
2015-04-20 15:45     ` Valdis.Kletnieks at vt.edu [this message]
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=6428.1429544726@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --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).