Brad Campbell wrote:

>Manu Abraham wrote:
>  
>
>>Moeen Alinaghian wrote:
>>
>>    
>>
>>>I think this book is what exactly you want
>>>Linux Device Drivers, O'REILLY Press
>>>      
>>>
>>The Linux kernel is a moving target, quite a lot of information in that 
>>book is quite outdated, but can give you an idea of things in there, 
>>rather than pointing to the actual kernel API.
>>
>>The best way to get into kernel programming is by reading the book to 
>>get a general idea about kernel programming, rather than to get know the 
>>actual kernel API. Later on, you can read the kernel code, and discuss 
>>issues on LKML.
>>    
>>
>
>Manu, Manu, Manu... you know better than most... Too modest dude!
>
>The best way to get into kernel programming is to dive in and do it..
>
>  
>

Yeah, you are right. i did not want to make it loud.

>I wonder how many times you blew/blow up your kernel in the processes of the 
>driver writing you do?
>I know every time I dive in to do some hacking I learn a lot, blow up the 
>machine numerous times and 
>have a lot of fun..
>  
>

The even more fun comes in when somebody has a bug and you _have_ to 
find that bug, well that time you might be really cornered.
You start getting pressures from different parts of the globe, depending 
on the number of users of your code.

But one very important thing i forgot to say, regular backups is one of 
the most necessary aspects.
The real fun comes in when you've conquered some nasty bug, The nastier 
it is, the more fun it is ..
But sometimes can prove expensive too ..

>When you get *really* familiar with the code you are working with, you get to 
>the point you know 
>exactly where the bug is by watching the stack backtrace as the 
>oops/panic/BUG_ON() scrolls past :p)
>  
>

At one point, if you know your code quite well, you will even know 
hotspots, even without running it, in many cases. just a description of 
the bug and without running it , itself you will be able to point it 
out. That stage, you will start loosing interest in that part of the 
code, since you get the feeling that you conquered it.

>Linux kernel hacking is great fun and can be a good way to blow away too many 
>hours of valuable time..
>
>As the Nike ad says.. "Just Do It".
>
>Find an itch and scratch it :p)
>  
>

Rather than saying great fun, i would term it as fun on the edge. 
Moreover it can teach you a lot to handle stuff.

>Having said that, the O'Reilly book is a *great* leg up.. but as a reference.. 
>If you read it cover 
>to cover, very little will stick. If you refer to it as you start to 
>modify/panic your kernel you 
>will learn a great deal from it.
>
>Alt-Sysrq, Serial Console, panic=10 and the reset button will be your guides.. 
>fsck your second best 
>friend and a decent bootloader with a safe/sane kernel will be your best 
>friend.
>
>Make frequent backups of your root filesystem, don't ever think "This code 
>can't possible corrupt my 
>filesystem" and take the odd break with a Vodka Martini or good Scotch to 
>ruminate on your code and 
>you will learn much grasshopper.
>
>  
>

Especially when kernel code starts overwriting memory and into your 
"favourite" ;-) Er.. Ehhmmm DMA buffer, we will see the real fun rolling 
downhill. Time to curse yourself.

>Use google as your guide, learn to quote, not to top-post, to post patches 
>in-line without wrap/tab 
>munging and don your flameproof undies prior to posting anything to the Kernel 
>Mailing list, and all 
>should be a smoothish ride..
>
>Like anything in life, Cars, Bikes, Boats, Lawn Mowers, Women.. breaking it 
>and then learning to fix 
>it is one of the best ways to learn.. certainly fun in any case..
>
>Speaking of breaking it.. if anyone wants to take the opportunity to have a 
>squiz inside a Ducati 4V 
>Desmodromic head/valve train, or other collected parts of what used to be a 
>bike, give me a yell..
>  
>

Add it to the personal museum, probably .. ;-) talking about personal 
museums, i have added a lot of "pre-alpha" DVB hardware of different 
colours shapes and sizes.. Recently i received some cards for the aspect 
of dismantling alone. Probably we have a chance of making some new 
techno-uber-geek hardware with all the dismantled pieces.. :-)


Manu



------------------------ Yahoo! Groups Sponsor --------------------~--> 
Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life.
http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/0XFolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/dubailug/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to