From: andrej.skvortzov@gmail.com (Andrey Skvortsov)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Are these books outdated?
Date: Thu, 14 Jul 2016 17:25:10 +0300 [thread overview]
Message-ID: <20160714142510.GD20923@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.20.1607140941220.14158@localhost.localdomain>
On 14 Jul, Robert P. J. Day wrote:
> On Thu, 14 Jul 2016, Rami Rosen wrote:
>
> > Hi,
>
> > Since there was a concern about these books being outdated, I want
> > to mention here also a book titled "Professional Linux Kernel
> > Architecture", by Wolfgang Maurer, Wiley, 2008, 1368 pages. (I read
> > it partially) And also I agree with Robert saying that he wouldn't
> > count on that publication date of LDD4 by Oreilly, since indeed the
> > publication date was postponed in the past (at least once but maybe
> > more, I am unsure about that)
>
> first, i wouldn't put any stock in a tentative publication date for
> LDD4, as i have already offered to be a technical pre-publication
> reviewer for that book, and i have been informed that there is no
> guarantee that there will be a new version of that book.
>
> (frankly, i would doubt it only because there would be *so* *much*
> content, it would be hard to pack all that into a single book. i can't
> even imagine trying to list everything one would have to cover in that
> newer version.)
>
> however, there are some git repos for the examples in LDD3 that were
> being updated to keep up with the kernel source -- here is one of
> them:
>
> https://github.com/martinezjavier/ldd3
>
> i don't know if that code is still maintained, but it's definitely
> more relevant than the code snippets from the original LDD3.
Here is link to Jessica McKellar's (LDD4 co-author) repo with examples
for the next book.
https://github.com/jesstess/ldd4
I'm not sure whether these examples are complete and in a good shape.
--
Best regards,
Andrey Skvortsov
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160714/f89fc7ba/attachment.bin
next prev parent reply other threads:[~2016-07-14 14:25 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 [this message]
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
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=20160714142510.GD20923@localhost.localdomain \
--to=andrej.skvortzov@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).