public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@devicelogics.com>
To: krishna <krishna.c@globaledgesoft.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: How to understand flow of kernel code
Date: Thu, 02 Dec 2004 09:11:47 -0700	[thread overview]
Message-ID: <41AF3EC3.7060807@devicelogics.com> (raw)
In-Reply-To: <41AE9E3E.9020307@globaledgesoft.com>


Hare Krishna, Hare Krishna, Krishna, Krishna, Hare, Hare,
Hare Rama, Hare Rama, Rama, Rama, Hare, Hare.

Start at entry.S and head.S in /arch/i386/kernel and trace the 
initialization. It's a good place
to start for understanding how the kernel boots and follow the code 
through init. Check out
the userspace interaction as well. It will at least start you with the 
basics.

You may want to offer a leaf, fruit, flower, and water to Lord Chaitanya 
and Lord Krishna
and chant the mantras in between to ask for guidance and understanding 
(I'm serious).

Interesting trivia. Krishna in hindi means "all attractive". The Greeks 
took the word and
over time it was corrupted into the word "Christ" which was later used 
for Jesus of Nazereth.
I lot of people probably don't know his last name actually came from the 
Vedic culture.

Hare Krishna,

Jeff

krishna wrote:

> Hi,
>
> Can Anyone tell me the tips/tricks/techniques/practices followed in 
> understanding flow of Linux kernel code?
>
> Regards,
> Krishna Chaitanya
> -
> 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/
>


  parent reply	other threads:[~2004-12-02 16:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-02  4:46 How to understand flow of kernel code krishna
2004-12-02  6:21 ` Bernd Eckenfels
2004-12-02 16:11 ` Jeff V. Merkey [this message]
2004-12-04 12:55   ` [OT] " Andries Brouwer
2004-12-04 16:39   ` Manu Abraham
2004-12-04 14:51 ` Jon Masters
2004-12-27 20:22 ` David Eger
  -- strict thread matches above, loose matches on Subject: below --
2004-12-02 18:28 Nick Warne
2004-12-02 19:13 ` Randy.Dunlap
2004-12-02 19:48   ` Cal Peake
2004-12-03 15:09 krishna
2004-12-03 15:27 ` Josh Boyer
2004-12-06 14:22 krishna
2004-12-06 18:49 ` Jon Masters

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=41AF3EC3.7060807@devicelogics.com \
    --to=jmerkey@devicelogics.com \
    --cc=krishna.c@globaledgesoft.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