From: "Christopher Friesen" <cfriesen@nortel.com>
To: ereslibre@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] Starting studying linux kernel
Date: Wed, 14 Sep 2005 16:10:54 -0600 [thread overview]
Message-ID: <43289FEE.7050409@nortel.com> (raw)
In-Reply-To: <93f85fee0509141449a0b702c@mail.gmail.com>
Rafael Fernández López wrote:
> Now, I am starting to read linux kernel, but it is so big that I
> cannot understand lots of things. I'd like to know if there is a
> website or something that can introduce me into the kernel internals.
>
> Maybe long time ago I could have understood it, but today it's so big...
You might try reading the following books:
http://lwn.net/Kernel/LDD3/
http://www.amazon.com/exec/obidos/tg/detail/-/0672327201/103-6781097-8768660?v=glance
http://www.amazon.com/exec/obidos/tg/detail/-/0596002130/ref=pd_sim_1/103-6781097-8768660?%5Fencoding=UTF8&v=glance
(this last one is based on 2.4)
Chris
prev parent reply other threads:[~2005-09-14 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 21:49 [OT] Starting studying linux kernel Rafael Fernández López
2005-09-14 20:46 ` jmerkey
2005-09-15 6:49 ` Chris White
2005-09-14 21:57 ` Michal Piotrowski
2005-09-14 22:10 ` Christopher Friesen [this message]
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=43289FEE.7050409@nortel.com \
--to=cfriesen@nortel.com \
--cc=ereslibre@gmail.com \
--cc=linux-kernel@vger.kernel.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