mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: alad@hss.hns.com
To: "Xiong Zhao" <xz@gatekeeper.ncic.ac.cn>
Cc: majordomo linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: kernel newbie question
Date: Sat, 28 Apr 2001 17:09:27 +0530	[thread overview]
Message-ID: <65256A3C.003F63C5.00@sandesh.hss.hns.com> (raw)



Hi Xiong,
     you can get a lot of books on kernel internals... But my experience says...
reading code is the best solution....all the intricacies can only be cleared
when u hack the code....
btw a new "understanding the linux kernel" by O'reilly pub. can be helpful in
'code reading'.

Amol




"Xiong Zhao" <xz@gatekeeper.ncic.ac.cn> on 04/28/2001 01:46:34 PM

To:   majordomo linux kernel list <linux-kernel@vger.kernel.org>
cc:    (bcc: Amol Lad/HSS)

Subject:  kernel newbie question




hello. i read linux kernel internal. are there other books/papers
like that which dwell with linux kernel in detail,especially on
process mechanism,for example,how pthread and fork are implemented,
how clone actually work.are there other materials on these topics
on internet that can be downloaded freely.


thanks


james

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/





             reply	other threads:[~2001-04-28 11:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-28 11:39 alad [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-28  7:16 Xiong Zhao
2001-04-28 12:55 ` Erik Mouw
2001-04-28 13:36   ` John Levon
2001-04-28 17:05     ` David Woodhouse

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=65256A3C.003F63C5.00@sandesh.hss.hns.com \
    --to=alad@hss.hns.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xz@gatekeeper.ncic.ac.cn \
    /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

all inboxes | Powered by JetHome®