All of lore.kernel.org
 help / color / mirror / Atom feed
From: nitric.acid@gmx.us (KK)
To: kernelnewbies@lists.kernelnewbies.org
Subject: how to compile the 0.01 version of kernel
Date: Sun, 09 Jan 2011 22:48:56 +0530	[thread overview]
Message-ID: <4D29EE00.4050901@gmx.us> (raw)
In-Reply-To: <AANLkTik83b8=03BDMY+y1B4BJupxK3OUZTrBFptptcZL@mail.gmail.com>

On 1/9/2011 9:41 PM, Javier Martinez Canillas wrote:
> Hello,
>
>> Then the next thing I was trying to do was to compile the source code
>> and try to understand the various methods/function calls, system calls
>> etc, but I'm not able to compile the code, I'm getting the following
>> errors:
>>
> If you want to compile this kernel to understand how an operating
> system works. I would recommend using a newer kernel version that you
> can easily compile and test with current tools. Compiling a 0.01 with
> today tools will be a pain and you would learn more about C compiling
> and linking than operating system internals.
>
> The Linux kernel is a really complex beast but also it is highly
> modularized, so you can try to understand one aspect at a time. Also
> there is much more documentation about recent kernels code that for a
> kernel that old.
>
> I would recommend buying some of the excellent books about Linux
> kernel internals, the best book in my opinion is Robert Love's Linux
> Kernel Development (http://amzn.to/i34vbB).
>
> Another great books  are Linux Device Drivers
> (http://lwn.net/Kernel/LDD3/), Essential Linux Device Drivers
> (http://amzn.to/bvELFI) and IA-64 Linux Kernel: Design and
> Implementation (http://amzn.to/fTvV9z). Also lwn.net site has a lot of
> documentation about the kernel in its Kernel index page
> (http://lwn.net/Kernel/Index/).
>
> I think that reading about the kernel internals while looking at the
> source code and latter trying to hack the code is the best way to
> learn about the Linux kernel an operating systems internals.
>
Thanks for your suggestion, Martinez. You got me right, basically I want 
to learn the more about the linux kernel internals. I know the its 
almost next to impossible to get a good grasp of the current kernel, I 
thought may be I should start with the older kernels and try to get good 
basic understanding, play around  and thereby learn things.
and once I've got a decent understanding of things I'll select any 
particular module of my interest and go ahead digging deeper in that 
particular section. I dint know that compiling the older kernel is such 
a pain and yes this exercise will end up learning more on 
compilation/linking etc and not what I exactly want.

Thanks for your suggestion. I'm going to buy some really good book in 
linux kernel and start learning and hacking.  Please let me know if you 
have any other suggestion on learning linux kernel internals.


Thanks,
KK.

  reply	other threads:[~2011-01-09 17:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-09 15:14 how to compile the 0.01 version of kernel KK
2011-01-09 16:11 ` Javier Martinez Canillas
2011-01-09 17:18   ` KK [this message]
2011-01-09 16:19 ` loody
2011-01-09 16:32 ` Robert P. J. Day
2011-01-09 22:39   ` Berlin Brown
2011-01-10  4:04     ` KK
2011-01-10  4:54       ` Berlin Brown
2011-01-09 16:40 ` Denis Kirjanov
2011-01-09 17:20   ` KK
2011-01-09 18:30 ` 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=4D29EE00.4050901@gmx.us \
    --to=nitric.acid@gmx.us \
    --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.