How to get the timestamp of linux kernel?

For Linux kernel hackers, how did you get into kernel development?

  • Do you remember the first patch that was accepted? How long were you involved in the community before submitting your first change? What is your day job? What was one piece of resource that helped you a lot during the development?

  • Answer:

    Fixing some compile error is a good start. You can also try other easy tasks from kernelnewbies: http://kernelnewbies.org/

Cong Wang at Quora Visit the source

Was this solution helpful to you?

Other answers

Back in 2000 when I were 17, out of curiosity I encouraged myself to try the bleeding edge Linux 2.4 tree of that time. I discovered a bug, sent a patch ( https://lkml.org/lkml/2000/8/8/145 ), and Linus responded. My first patch was not the best, but it led to the problem being identified and fixed. I gained a lot of technical depth and insights by reading lengthy LKML threads in which kernel development is discussed by the devs, especially threads in which Linus Torvalds participates (ignoring the occasional profanities, that's for entertainment). Eventually it became one of my main fields of expertise. Reading the mailing list of an open source project before contributing is important, because usually the do-and-don'ts are there first -- before they get officially documented, and you can better understand how they reached their conclusions.

Dan Aloni

My approach is usually a head-on one. Well i would suggest taking up one particular driver or subsystem in linux kernel. Try obtaining the linux source code for ur linux distribution or the development board you are using Try building it, making it boot up (will feel great when something you built boots up first :) ) Now that you got your kernel up and running, lets try messing with it:) understand how to configure - enable and disable a feature in compile time and then later on runtime controlling logging behaviour of kernel - debug messages Pick a particular module - for instance display driver or scheduler or memory allocator. Its your choice. Enable full logs for the module that you are trying to understand Filter the logs and observe its runtime behaviour Before jumping in to coding and other hardcore always observe the runtime behavior, that will give you an overview of how it works. Later you can co-relate it to the code and get an in depth view. Hope this will get you started

Vaisakh Sudheesh

Here, is my story of getting in to kernel development to becoming a Linux Kernel engineer:http://www.cio.com/article/3012310/linux/how-one-girl-is-making-good-on-her-dream-to-become-a-linux-kernel-engineer.htmlAs far as it is a matter of resources, you can go for my following Quora answer:

Vaishali Thakkar

Just Added Q & A:

Find solution

For every problem there is a solution! Proved by Solucija.

  • Got an issue and looking for advice?

  • Ask Solucija to search every corner of the Web for help.

  • Get workable solutions and helpful tips in a moment.

Just ask Solucija about an issue you face and immediately get a list of ready solutions, answers and tips from other Internet users. We always provide the most suitable and complete answer to your question at the top, along with a few good alternatives below.