From: Jeff.Haran@citrix.com (Jeff Haran)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Learning things
Date: Mon, 6 Apr 2015 17:14:09 +0000 [thread overview]
Message-ID: <4E5779AD88B2F040B8A7E83ECF544D1A5C93AB@SJCPEX01CL03.citrite.net> (raw)
In-Reply-To: <5522BD47.1070904@gmail.com>
-----Original Message-----
From: kernelnewbies-bounces@kernelnewbies.org [mailto:kernelnewbies-bounces at kernelnewbies.org] On Behalf Of Joris Bolsens
Sent: Monday, April 06, 2015 10:07 AM
To: Valdis.Kletnieks at vt.edu
Cc: kernelnewbies at kernelnewbies.org
Subject: Re: Learning things
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
In that case do you have any general recommendations? Or is there some sort of project that covers most of the basics? I learn best by doing and most stuff I found online goes pretty slow and is a bit boring :/
Thanks a ton
On 04/06/2015 10:02 AM, Valdis.Kletnieks at vt.edu wrote:
> On Mon, 06 Apr 2015 10:43:46 -0700, Joris Bolsens said:
>
>> I'm working on trying to teach myself C and was wondering if you had
>> any kernel specific recommendations.
>
> Don't bother trying until you have an actual good working knowledge of
> C.
>
> Work in userspace where your screw-ups just take the process out, not
> the entire system, until stuff like a SIGSEGV becomes a rarity.
> *THEN* start considering kernel work.
>
A google search on "open source projects written in c" yielded this:
http://www.quora.com/What-are-open-source-projects-that-are-written-in-C-C++-are-easy-to-contribute-to
Jeff Haran
next prev parent reply other threads:[~2015-04-06 17:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 17:43 Learning things Joris Bolsens
2015-04-06 17:02 ` Valdis.Kletnieks at vt.edu
2015-04-06 17:07 ` Joris Bolsens
2015-04-06 17:14 ` Jeff Haran [this message]
2015-04-06 23:09 ` Joris Bolsens
2015-04-06 17:05 ` Jeff Haran
2015-04-06 17:17 ` Greg KH
2015-04-06 18:38 ` Mike Thompson
2015-04-07 4:06 ` Anupam Kapoor
2015-04-07 12:43 ` Malte Vesper
2015-04-07 13:56 ` Miles Fidelman
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=4E5779AD88B2F040B8A7E83ECF544D1A5C93AB@SJCPEX01CL03.citrite.net \
--to=jeff.haran@citrix.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.