From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Resources to teach from C to Kernel Development?
Date: Tue, 02 Sep 2014 11:37:52 -0400 [thread overview]
Message-ID: <3880.1409672272@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 28 Aug 2014 20:49:01 +0100." <1BC7FEE4-3A71-486A-9355-27F1732F6C43@icloud.com>
On Thu, 28 Aug 2014 20:49:01 +0100, Ed Holmes said:
> Can you recommend me any books or online resources to teach a C programmer
> Kernel development? I can program in C but I don't really know where to go from
> there. I've tried the Eucalyptus challenge but it just suggests things to try.
> No actual tutorial.
Kernel development is a field that isn't very friendly to people who need
tutorials, sorry. There's a few things like LDD3 and the Eudyptula stuff, but
in general you really need to be the sort of programmer who can figure this
stuff out for themselves, because APIs are *constantly* being changed, updated,
and added/removed. LDD3 is pretty much as good as it gets, and even that gets
outdated because we're moving along at about a million lines a release. So
there's a good amount of "sink or swim" involved here.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140902/b1cb04a5/attachment.bin
next prev parent reply other threads:[~2014-09-02 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 19:49 Resources to teach from C to Kernel Development? Ed Holmes
2014-09-02 1:03 ` Raphael Philipe
2014-09-02 15:37 ` Valdis.Kletnieks at vt.edu [this message]
2014-09-02 18:22 ` nick
2014-09-02 18:24 ` John de la Garza
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=3880.1409672272@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--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.