Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am new in kernel development and good enough in c programming.
I just want to know should i start with latest kernel version or is there any basic kernel version that help me to understand basics of kernel development easily ?
I want some suggestions regarding kernel development. Searching past threads not solved my query
Yes, good place to start.
As for the kernel, I reckon you should just go grab the latest stable 2.6 one. Development is (extremely) active, no point starting with something older. As you will see recommended elsewhere, I suggest you pick an area you are interested in and concentrate on that. You will get overwhelmed otherwise - probably will happen anyway, but limit yourself for a start.
Thanks all of you for response.
What u mean by Concentrating in an area? does it mean to limit, for example file system or memory management section of kernel development
Hi,
If you have linux kernel Development 2nd edition book the author is Robert love please go through it because before you starting and hacking the kernel first get some book knowledge then go through the code, selecting linux version doesn't make much sense anyhow take the older one like 2.6.x.x, so go through the book while reading if you want to see the code then you can,but don't get dishearted n stand up to it, i'm sure one day you are the person fell free to say any answers in the kernel, I wish you did well
Just saw this thread again because of IND response (I had unsubscribed).
Quote:
What u mean by Concentrating in an area? does it mean to limit, for example file system or memory management section of kernel development
Yes, that was what I had meant. There is so much code, you'll probably find it easier if you can find something you are interested in. You'll find yourself having to dive into other areas of the code anyway. And as IND indicated, having a book or two handy is useful.
Dive in. Take your life-preserver with you. Consider wedging yourself into a barrel. An oxygen cylinder might be useful. So might a couple of magic wands with rusty stars on their ends. If you know any magic words (or hear any hollow voices), write down whatever words they say.
One way or the other, somewhere down the line, you will bob back up to the surface ... having lost more than a few hair-follicles in the process. However, you will be among friends. Some people even might start calling you a ... which is some small consolation.
It will definitely give you a new degree of respect for Linus Torvalds.
The downside is, even after all you've been through, you still can't discuss it at dinner-parties. No one will understand you. (And maybe you won't mind. Maybe you'll be heard from time to time muttering under your breath about "lesser beings and PHP programmers.")
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.