mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Vadim Lobanov <vadim@cs.washington.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Starting project.
Date: Fri, 21 May 2004 20:46:18 -0700	[thread overview]
Message-ID: <20040521204618.6a89ddf9.rddunlap@osdl.org> (raw)
In-Reply-To: <20040521201011.D8524-100000@attu4.cs.washington.edu>

On Fri, 21 May 2004 20:22:15 -0700 (PDT) Vadim Lobanov <vadim@cs.washington.edu> wrote:

| Hello,
| 
| Up to now, I've been reading up on various outside sources about the 
| structure of the Linux kernel, as well as following the discussions on 
| this list. Though so far I've only had experience at writing userland 
| programs on *nixes, I've acquired a curiosity for the overall structure of 
| the kernel, the algorithms it uses, and its evolution over time. Though I 
| know the theory behind operating systems in general, I'd like to get some 
| hands-on practice. For this reason, I am curious if a list of pending 
| TODOs/projects relating to the kernel or drivers is maintained anywhere,
| such that I could pick a simple one to try to work on, for starters. After 
| all, the best way to learn is to dive right in. :)

It depends.  on your interest level, project goals(s)/size, etc.
BTW, please use 2.6.x for anything new that you do.

There are current iSCSI and Infiniband driver projects underway.
These are attempts to add fairly large, new drivers to the kernel.

For a list of smaller, get-your-feet-wet projects, you could consider
some of these:

- the current must-fix list, which is kept in the latest
	-mm tree patch; current file is here (but there is
	no permanent URL for it):
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6/2.6.6-mm4/broken-out/must-fix.patch

the current kernel-janitors project TODO list:
http://janitor.kernelnewbies.org/TODO
(but check on their mailing list before taking one of these on)

Bug reports from the Stanford Checker project, but these are mostly
email postings*, not web postings:
http://metacomp.stanford.edu/

Bug reports from the Coverity people (like Checker):
http://www.coverity.com/main.html
but mostly email postings*

Bug reports from the OPERA project (similar to Checker, but from
UIUC):	http://carmen.cs.uiuc.edu/
but mostly email postings*

Current bugs in the kernel bugzilla database:
http://bugzilla.kernel.org/

Some projects maintain their own TODO list.  If there are some areas
that you are particularly interested in, check with them to see if
they have a TODO list.

--
~Randy

      reply	other threads:[~2004-05-22  3:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-22  3:22 Vadim Lobanov
2004-05-22  3:46 ` Randy.Dunlap [this message]

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=20040521204618.6a89ddf9.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vadim@cs.washington.edu \
    /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

all inboxes | Powered by JetHome®