From: Jiri Slaby <slaby@liberouter.org>
To: Weber Ress <ress.weber@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Education
Date: Mon, 09 Jan 2006 14:21:27 +0100 [thread overview]
Message-ID: <43C26357.9050301@liberouter.org> (raw)
In-Reply-To: <9c2327970601090500i78fec178mb197c0fa5732e4a4@mail.gmail.com>
Weber Ress napsal(a):
> Hi guys,
>
> I´m starting a social project to teach kernel development for young
> students, with objetive of include these people in job market.
:)
>
> These studentes don´t have great skills in mathematical and computer
> science areas, but have great interest in development area. Some
> studentes have a little basic C language skills.
>
> Which are the first steps that I need in this project ?
prepare slides for teaching them real-world-(gc)c, not basic.
> Which´s the "more simple" kernel version to teach (2.2 ? 2.4 ? 2.6 ?).
IMHO 2.6 has the clearest api (specific(a) rather than sth. like
a->private->b->private.specific).
But in general it's hard to say this is the simplest one. In 2.2 there is less
code, than in 2.6 and so on
regards,
--
Jiri Slaby www.fi.muni.cz/~xslaby
\_.-^-._ jirislaby@gmail.com _.-^-._/
B67499670407CE62ACC8 22A032CC55C339D47A7E
next prev parent reply other threads:[~2006-01-09 13:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 13:00 Kernel Education Weber Ress
2006-01-09 13:21 ` Jiri Slaby [this message]
2006-01-09 13:25 ` Weber Ress
2006-01-09 13:30 ` Kasper Sandberg
2006-01-09 16:59 ` Jiri Slaby
[not found] ` <Pine.LNX.4.61.0601090805140.17451@chaos.analogic.com>
2006-01-11 18:42 ` Weber Ress
2006-01-11 20:37 ` linux-os (Dick Johnson)
2006-01-12 7:59 ` Peter Bortas
2006-01-13 22:37 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-01-09 13:35 Khushil Dep
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=43C26357.9050301@liberouter.org \
--to=slaby@liberouter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ress.weber@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox