From: abhi.c.pawar@gmail.com (Abhijit Pawar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Best and fastest way to understand kernel subsystem ?
Date: Thu, 06 Dec 2012 17:44:30 +0530 [thread overview]
Message-ID: <50C08C26.300@gmail.com> (raw)
In-Reply-To: <962931354795372@web11e.yandex.ru>
On 12/06/2012 05:32 PM, rush wrote:
> Hi,
> Most of O'Reilly books are pretty old. Afair the latest O'Reilly book is from
> Robert Love about 2.6.34. Does it make sense?
Yes. Its a good book.
> Or even book 2005 are still usefull?
Even if the books are older they can give you the general idea about the
thoughts put into the particular subsystem.
> -- rush
> 06.12.2012, 15:49, "Abhijit Pawar" <abhi.c.pawar@gmail.com>:
>>
>> On 12/06/2012 03:24 PM, Shraddha Kamat wrote:
>>
>> What is the best (and the fastest ) way to understand a kernel
>> subsystem ( for e.g., filesystem , Networking .. etc.)
>>
>> Reading the kernel code is the best way. For reference you can use LDD3
>> and books from OReilly.
>>
>> -- Shraddha
>>
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org <mailto:Kernelnewbies@kernelnewbies.org>
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>> --
>> -
>> Abhijit
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org <mailto:Kernelnewbies@kernelnewbies.org>
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>
--
-
Abhijit
next prev parent reply other threads:[~2012-12-06 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 9:54 Best and fastest way to understand kernel subsystem ? Shraddha Kamat
2012-12-06 11:46 ` Abhijit Pawar
2012-12-06 12:02 ` rush
2012-12-06 12:14 ` Abhijit Pawar [this message]
2012-12-06 12:53 ` Matthias Brugger
2012-12-06 13:34 ` Anuz Pratap Singh Tomar
2012-12-07 4:52 ` sanjeev sharma
2012-12-08 16:31 ` Mulyadi Santosa
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=50C08C26.300@gmail.com \
--to=abhi.c.pawar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.