From: Jim Nelson <james4765@verizon.net>
To: Eugene K <evgfpeters@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to start
Date: Sat, 01 Jan 2005 22:26:06 -0500 [thread overview]
Message-ID: <41D769CE.1070902@verizon.net> (raw)
In-Reply-To: <20050102030444.51206.qmail@web51002.mail.yahoo.com>
Eugene K wrote:
> For many years I've been involved in OS/kernel and
> network development on various platforms (including
> Intel86) and OSes, but I am totally new to Linux. What
> would be an optimal way for somebody like me to learn
> both Linux driver development and Linux Kernel
> internals ?
>
>
Hit http://www.dit.upm.es/~jmseyas/linux/kernel/hackers-docs.html - has a good
selection of dead-tree and online references. The kernel-janitors project -
http://www.kerneljanitors.org/ - is a good starting point; that's where a lot of
kernel hackers get their start.
next prev parent reply other threads:[~2005-01-02 3:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-02 3:04 How to start Eugene K
2005-01-02 3:26 ` Jim Nelson [this message]
2005-01-02 13:38 ` Pedro Venda
2005-01-02 13:39 ` Pedro Venda
2005-01-02 14:36 ` Christoph Anton Mitterer
2005-01-02 14:31 ` Lethalman
-- strict thread matches above, loose matches on Subject: below --
2005-01-03 6:22 Kotian, Deepak
2005-01-03 15:13 ` Jonathan Corbet
2005-01-04 7:26 Kotian, Deepak
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=41D769CE.1070902@verizon.net \
--to=james4765@verizon.net \
--cc=evgfpeters@yahoo.com \
--cc=linux-kernel@vger.kernel.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