All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Weber <weber@nyc.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: In great need
Date: Thu, 25 Oct 2001 12:14:04 -0400	[thread overview]
Message-ID: <3BD83A4C.B435D9DC@nyc.rr.com> (raw)
In-Reply-To: <fa.jh1e0kv.4k8ujg@ifi.uio.no>

I am a newbie/wannabe kernel hacker too :). 

Here are the steps I plan to take:

[1] Take an Operating Systems class (or read through the 
syllabus materials).
[2] Write a small operating system (to learn the stuff 
that OS courses/books don't teach... for example, it 
took me a while to realize where the BIOS loads the 
MBR... thank god lilo is open source).
[3] Learn a little about hardware and hardware 
standards like PCI, PCMCIA, ACPI, USB, etc.
[4] Read Oreilly's "Understanding the Linux Kernel".
[5] Read the linux-kernel FAQ and archives
[6] Read linux-kernel@vger.kernel.org (No Posting!)
[7] Read linux source code
[8] Read linux-kernel@vger.kernel.org (Post at Will!!)
[9] Identify an area of need
[10] Write code
[11] Sacrifice a virgin pigeon and drink milk of an 
albino goat....

You are now a kernel hacker.

I'm at step 2... perhaps as I go further a few of the 
steps will disappear :).  Just my $0.02.

Patrick Ouellet wrote:
> 
> Hi to you all great Linux Kernel maintainers.
> 
> As a follower of linux for a couple of years now
> I wanted to go deeper into the madness,
> so I said to myself, why no go as deep as you
> can and get yourself into the Kernel.
> 
> My simple question is this:
> 
> Were should I start.
> I would like to have a nice overview of the kernel
> something that would help me understand all the part
> of the kernel and how they work toghether.
> 
> If anyone could tell me where I could get
> such information.. I would be pleased.
> 
> Thanx to you all and keep up the good work.
> 
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==
> -=-=-=-=-=-=
> Patrick Ouellet - Programmeur Sénior
> patrick.ouellet@microtecsecurite.com
> Recherche & Devloppement
> Les Entreprise Microtec inc.
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==
> -=-=-=-=-=-=
> "First they ignore you. Then they laugh at you.
> Then they fight you. Then you win."
> -Mohandas Gandhi
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==
> -=-=-=-=-=-=
> All source code included (if any ) is
> copyright Microtec Technologies Inc. 2001
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==
> -=-=-=-=-=-=
> 
> -
> 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-10-25 16:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.jh1e0kv.4k8ujg@ifi.uio.no>
2001-10-25 16:14 ` John Weber [this message]
2001-10-25 15:32 In great need Patrick Ouellet
2001-10-25 15:58 ` Rik van Riel
2001-10-25 18:52   ` Daniel Phillips
2001-10-25 19:37     ` EvilTypeGuy
2001-10-25 19:45       ` Jonathan Corbet
2001-10-25 19:54         ` Tahar
2001-10-25 20:08         ` EvilTypeGuy
2001-10-25 20:13           ` Robert Love
2001-10-25 16:34 ` Jonathan Corbet
2001-10-25 20:10   ` Daniel Phillips

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=3BD83A4C.B435D9DC@nyc.rr.com \
    --to=weber@nyc.rr.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 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.