From: malte.vesper@postgrad.manchester.ac.uk (Malte Vesper)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Learning things
Date: Tue, 07 Apr 2015 13:43:25 +0100 [thread overview]
Message-ID: <5523D0ED.6000502@postgrad.manchester.ac.uk> (raw)
In-Reply-To: <876198lgys.fsf@fatcat.parallelwireless>
On 07/04/15 05:06, Anupam Kapoor wrote:
>>>>>> [2015-04-07T00:08:10+0530]: "Mike Thompson" (mike-thompson):
> ,----[ mike-thompson ]
> | As others mention, using the Linux kernel to come up to speed with C is the
> | wrong approach. If you have a strong desire to learn kernel programming
> | concepts while coming up to speed on C, I would suggest getting the latest
> | book on Xinu, buying an Intel Galileo board and working your way through
> | that book. Xinu is what I cut my teeth on 25 years ago and I remember it
> | being a terrific learning environment. Xinu is not Linux (or Unix), but
> | for starting at the ground level all the concepts will map over when you
> | are ready to tackle Linux kernel work.
> |
> | Information for Xinu can be found here: http://www.xinu.cs.purdue.edu/
> `----
> or there is always xv6 (http://pdos.csail.mit.edu/6.828/2014/) which
> might be useful...
>
There is also OS161 or Plan9, these should be enough names to search for
comparisons or discussions on the OS's to help you pick one.
next prev parent reply other threads:[~2015-04-07 12:43 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
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 [this message]
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=5523D0ED.6000502@postgrad.manchester.ac.uk \
--to=malte.vesper@postgrad.manchester.ac.uk \
--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.