From: cartercheng@gmail.com (Carter Cheng)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Fwd: Learning Linux Kernel Development
Date: Thu, 11 Oct 2018 13:56:59 +0800 [thread overview]
Message-ID: <CALS6=qUJsh0axBb9trT-GWCy030jEpc6b8wr9YqS4n9_fvebXQ@mail.gmail.com> (raw)
In-Reply-To: <15088.1539187406@turing-police.cc.vt.edu>
Thanks for the advice. I actually have those books as well and will take a
look at them.
On Thu, Oct 11, 2018 at 12:03 AM <valdis.kletnieks@vt.edu> wrote:
> On Wed, 10 Oct 2018 23:35:20 +0800, Carter Cheng said:
> > 1. After finishing the book and perhaps Understanding the Linux Kernel
> and
> > Linux Device Drivers. What is the best way to dig deeper.
>
> There's multiple answers to that question, as it depends on the
> questioner's preferred
> learning style and motivation for digging deeper.
>
> (I'll just add a link so I don't have to copy-paste here)
>
> https://lists.kernelnewbies.org/pipermail/kernelnewbies/2017-April/017765.html
>
> > 2. Is there some good way to figure out how to update knowledge gained
> from
> > this book to what is in the 4.x series of kernels?
>
> If you've studied enough different kernels so that you can generalize from
> an
> example, the fact that 4.19 is 12 million lines different from 2.6.whatever
> won't be much of an issue. If however you're still at the cargo-cult
> programming level of writing code the way the LDD says via cut-n-paste
> without
> really understanding it, you're going to have a bad time.
>
> Somebody was keeping sample code from the LDD, updated to recent kernels.
> Not
> sure if it's much help - if you understand the concepts involved, you
> probably
> wouldn't need sample code, and if you didn't understand the concepts, you
> just
> end up cut-n-pasting from a newer version....
>
> (Two really good kernel books are Bach's book on the Unix SYSV kernel and
> McKusick's book on the BSD kernel - both spend a good amount of time doing
> "and
> if we don't take a lock here, this race condition can happen, and if it
> happens, *this* is what your file system looks like afterwards" type
> discussion...)
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20181011/638d2fa8/attachment.html>
next prev parent reply other threads:[~2018-10-11 5:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALS6=qW=eiPfeZ23uEBLTdtpdzsb4Y2biNuPZ-Hj9CzjQdJnDA@mail.gmail.com>
2018-10-10 15:35 ` Fwd: Learning Linux Kernel Development Carter Cheng
2018-10-10 16:03 ` valdis.kletnieks at vt.edu
2018-10-11 5:56 ` Carter Cheng [this message]
2018-10-11 10:42 ` o at goosey.org
2018-10-11 13:46 ` Carter Cheng
2018-10-12 2:05 ` valdis.kletnieks at vt.edu
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='CALS6=qUJsh0axBb9trT-GWCy030jEpc6b8wr9YqS4n9_fvebXQ@mail.gmail.com' \
--to=cartercheng@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).