All of lore.kernel.org
 help / color / mirror / Atom feed
From: rohan.puri15@gmail.com (Rohan Puri)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Beginner guide
Date: Wed, 11 Jun 2014 12:51:22 +0530	[thread overview]
Message-ID: <CALJfu6MSwfQLxRGz7eE1FMtgDspoowmW9tJhzo4_PERsg3N5yQ@mail.gmail.com> (raw)
In-Reply-To: <CA+aCy1G062J_oq7ipLs-B2NZDJVOuT28ESfwFPzcZTYTzO8Nvw@mail.gmail.com>

On Wed, Jun 11, 2014 at 12:35 PM, Pranay Srivastava <pranjas@gmail.com>
wrote:

> On Wed, Jun 11, 2014 at 11:58 AM, Prudhvee Narasimha Sadha
> <prudhvi.sada@gmail.com> wrote:
> > Hi,
> >       My name is Prudhvee and I'm purusing my undergraduate second year.
> I'm
> > intrested in kernel development but I'm unable to understand how to get
> into
> > it.
> > Can you please help me to become a kernel developer.
>
> I would suggest get the foundations right first and let's hope you know
> good C,
> tricks are good to know but you should be able to understand code
> written by others and be able to integrate the knowledge with what you
> already know.
>
> Agree. Ways to do this : -
1. Read/write/understand K&R C language.
2. To understand code written by others you have to start doing that. (I
mean practice it).


> If you haven't used semaphores or mutexes in user space code then do
> that first, understand why is the need. For example why you need to
> have a sycall to get a semaphore
> but when working with pthreads you probably don't need that.
>
> Understand compiler and make it your friend. Errors you get while
> compiling, and things you can do for example why  ((struct
> mystruct*)(0))->member fails when you run code but &(((struct
> mystruct*)(0))->member) works.
>
>

>
> Basic idea is to get to understand how would you do it yourself, get
> some ideas in your mind see if they should work or not. You may be
> able to write code maybe without going through all that but in the
> long run it would help.
>
> >
> >      I just want to know what I should learn and any suggested books to
> > learn kernel programming.
> >
>
> Take an operating system course first. Get to know the basics then you
> can try to understand kernel code. You can start with LDD, i think a
> new version is available now, but take an OS course in parallel or
> read yourself.
>
Agree. Ways to do this : -
Get an OS course done, search for courses online, 2 of ones which I know
are : -
1. http://www.cs.cmu.edu/~213/
2. CMUs OS course.

>
> >  Thank you,
> >  Prudhvee.
> >
> > _______________________________________________
> > Kernelnewbies mailing list
> > Kernelnewbies at kernelnewbies.org
> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> >
>
>
>
> --
>         ---P.K.S
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>

- Rohan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140611/53cb848f/attachment.html 

  reply	other threads:[~2014-06-11  7:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11  6:28 Beginner guide Prudhvee Narasimha Sadha
2014-06-11  6:47 ` Asutosh Das
2014-06-11  7:05 ` Pranay Srivastava
2014-06-11  7:21   ` Rohan Puri [this message]
2014-06-11 12:08     ` sanjeev sharma
2014-06-11 13:39 ` Ben
2014-06-11 14:55   ` Pranay Srivastava
2014-06-11 17:27     ` Saurabh Jain
2014-06-11 17:55 ` Valdis.Kletnieks at vt.edu
2014-06-11 18:04   ` Robert P. J. Day
  -- strict thread matches above, loose matches on Subject: below --
2013-05-29 13:24 Beginner Guide Jie Ping Quek
2013-05-29 13:48 ` Ian Campbell
2013-05-29 13:56   ` Ben Guthro
2013-05-30  7:52   ` Pasi Kärkkäinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALJfu6MSwfQLxRGz7eE1FMtgDspoowmW9tJhzo4_PERsg3N5yQ@mail.gmail.com \
    --to=rohan.puri15@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.