From: john.chludzinski@vivaldi.net (John Chludzinski)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Are these books outdated?
Date: Sun, 07 Aug 2016 09:29:01 -0400 [thread overview]
Message-ID: <156b7e5e8149927ea9f25e2c12d46aac@mail.vivaldi.net> (raw)
In-Reply-To: <20160714140155.62523307@fujitsu>
Linux Kernel Development by Robert Love
On 2016-07-14 07:01, Aleksander Alekseev wrote:
> Hello
>
> I'm a full-time *nix C developer. I have a pretty good idea how
> operating systems work. Still I would like learn more about Linux
> internals in particular, write a few device drivers, maybe some
> patches to kernel itself, etc. Here are a few books I've found:
>
> * Linux Kernel Development, 3rd Edition (2010)
> * Understanding the Linux Kernel, 3rd Edition (2005)
> * Linux Device Drivers, 3rd Edition (2005)
>
> Could you tell me please, are these books considered worth reading in
> year 2016 or they are completely out of date? Perhaps there are some
> newer books and/or tutorials you could recommend?
next prev parent reply other threads:[~2016-08-07 13:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 11:01 Are these books outdated? Aleksander Alekseev
2016-07-14 11:40 ` François
2016-07-24 10:58 ` Robert P. J. Day
2016-07-24 18:44 ` Greg KH
2016-07-14 11:43 ` Ricardo Ribalda Delgado
2016-07-14 11:50 ` François
2016-07-14 12:26 ` Robert P. J. Day
2016-07-14 12:49 ` Rami Rosen
2016-07-14 13:53 ` Robert P. J. Day
2016-07-14 14:25 ` Andrey Skvortsov
2016-07-14 14:44 ` Rami Rosen
2016-07-14 21:17 ` Kosta Zertsekel
2016-07-18 9:22 ` Raul Piper
2016-08-07 13:29 ` John Chludzinski [this message]
2016-08-10 17:46 ` Raul Piper
2016-08-10 18:14 ` John Chludzinski
2016-08-10 18:17 ` Greg KH
2016-08-10 18:21 ` John Chludzinski
2016-08-11 3:52 ` Raul Piper
2016-08-11 5:27 ` Stefan Wahren
2016-08-11 8:06 ` Aleksander Alekseev
2016-08-11 8:11 ` Raul Piper
2016-08-11 12:49 ` Raul Piper
2016-08-14 19:48 ` Andrey Skvortsov
2016-08-14 20:37 ` Stefan Wahren
2016-08-15 8:02 ` Aleksander Alekseev
2016-08-15 19:17 ` Raul Piper
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=156b7e5e8149927ea9f25e2c12d46aac@mail.vivaldi.net \
--to=john.chludzinski@vivaldi.net \
--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).