Slashdot Mirror

← Back to Stories (view on slashdot.org)

Becoming a Linux Kernel Programmer?

Posted by Cliff on from the take-many-slow-steps dept.

Young Grasshoopa asks: "In my 6 years of IT life, I've been a sys admin, perl programmer, and a config. mgmt. engineer. I've recently learned programming in C, and somehow ended up learning a bit of Linux Kernel programming as well. I now have developed a strong motivation to become a Linux kernel developer, but given my background, I am not sure how to approach companies or Open Source Project groups. I ask all those who were in a similar situation - how do you become a full-time kernel developer?"

4 of 52 comments (clear)

  1. Have you considered checking by leviramsey · · Score: 5, Informative

    KernelNewbies?

    If you have, you may want to consider starting out as a kernel janitor (basically doing assloads of grunt work to build a name for yourself).

  2. Kernel Development by kzadot · · Score: 5, Informative
    Well its a strange question to ask, normally one becomes a Kernel Developer, by having a need, usually unsupported hardware, and they write a driver for it.

    I would consider myself a kernel developer at this stage, even before my driver is included in the mainstream kernel versions.

    It sounds like you are at this stage already, so are you actually asking "How do I get a driver included in the kernel as distributed?". Well I think the answer to that is to keep submitting it to the maintainer of the relevant kernel. Things like revelance, and especially quality are important factors too.

    For anyone at an earlier stage, perhaps "normal" programmers who need to learn how it all works in the kernel, I have (reccomend is too strong a word, as I have only read these 2 books on the topic) read 2 OReilly books.

    Understanding the Linux Kernel, 2nd Edition and Linux Device Drivers, 2nd Edition

    Of course you should also be on the linux kernel mailing list

    And the rest is dependant on exactly you want to add to the kernel.

  3. Here's a way... by Anonymous Coward · · Score: 5, Insightful

    the easiest way would be
    to start as a part time kernel developer.

    find something wrong.
    fix it.
    find who's in charge of that code.
    send it to them.

    if there's not anyone,
    contact one of the high mucky-mucks,
    and let em know.
    maybe the maintainer will be you.

  4. getting acquanted by bmac · · Score: 5, Interesting

    Your best bet (not that I have done this or have any inclination to do so) may be to be a part of documenting the code area(s) you are interested in working on. This will thoroughly acquaint you with the code and provide a much-needed service that may get your foot in the door.

    Just a thought,
    bmac

    Peace be with you all.
    Manual .sig generator v.1.0.