Linux Kernel Development - A Practical Approach

Linux Kernel Development - A Practical Approach

[Linux "Kernel" Explorer]

[-- Attachment #1: Type: text/plain, Size: 790 bytes --]

Hello Everyone,

I am reading 'Linux Kernel Development' by Robert Love these days.

This book takes you on a theoretical journey of the linux kernel
world.Though the book is good but I do have my share of concerns.

   - I Understand theory is important but how to gain some practical
   experience.How to learn to apply the rules you have learnt in the book. I
   have got no clue.
   - Trying to dive into the kernel code and expecting things to make sense
   would be a little to premature.I will have to jump into the code ...but I
   guess its too early.
   - Should I be trying my hand at System programming first / Kernel user
   side to get a hand of things.Would it be a good idea ?

Would really appreciate your suggestion & Advice.

Thanks in advance,

Linux "Kernel" Explorer.

[-- Attachment #2: Type: text/html, Size: 946 bytes --]

Re: Linux Kernel Development - A Practical Approach

[Tapas Mishra]

On Tue, Oct 5, 2010 at 12:20 AM, Linux "Kernel" Explorer
<mylinuxlab@gmail.com> wrote:
> Hello Everyone,
>
> I am reading 'Linux Kernel Development' by Robert Love these days.
>
> This book takes you on a theoretical journey of the linux kernel
> world.Though the book is good but I do have my share of concerns.
Exactly even I do have same concerns.
www.crashcourse.ca
check the above website till today this is the only most relevant
thing which I find easy to begin with.
You can then go to understand some more howtos on internet that will help.
LKD is no doubt good book but even I do not appreciate that.
Jumping directly to code in your or even  mine type of situation is
not easy having said that I would say you not to
indulge into books.If possible get some one who can easily give you a
hands on experience.
Then you will be able to understand what the text books talk.
A good advice I got from some one who works with processors is rather
than going in manuals
jump into the code you play with it and then you will gradually understand.
There may be different views but I would suggest you not to read books.