public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kasper Sandberg <lkml@metanurb.dk>
To: Weber Ress <ress.weber@gmail.com>
Cc: Jiri Slaby <slaby@liberouter.org>, linux-kernel@vger.kernel.org
Subject: Re: Kernel Education
Date: Mon, 09 Jan 2006 14:30:15 +0100	[thread overview]
Message-ID: <1136813415.8412.0.camel@localhost> (raw)
In-Reply-To: <9c2327970601090525v5548034fh780455513b50e8c0@mail.gmail.com>

On Mon, 2006-01-09 at 11:25 -0200, Weber Ress wrote:
> When I say "more simple" kernel version, I would like say "more
> didactics" to teach.
> 
> thank´s to all replies.
> 
> Best,
> 
> Weber Ress
> 
> On 1/9/06, Jiri Slaby <slaby@liberouter.org> wrote:
> > 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 ?).
well.. if they were ever to do anything useful with it, it would
basically have to be the newest, alot things have changed in 2.2 to 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
> >
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  reply	other threads:[~2006-01-09 13:30 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
2006-01-09 13:25   ` Weber Ress
2006-01-09 13:30     ` Kasper Sandberg [this message]
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=1136813415.8412.0.camel@localhost \
    --to=lkml@metanurb.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ress.weber@gmail.com \
    --cc=slaby@liberouter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox