From: Pedro Diaz Jimenez <pdiaz88@terra.es>
To: Jeff Garzik <jgarzik@mandrakesoft.mandrakesoft.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Beware - kernel Newbie!
Date: Mon, 19 Feb 2001 00:17:49 +0100 [thread overview]
Message-ID: <01021900174905.00315@tajo> (raw)
In-Reply-To: <Pine.LNX.3.96.1010218165420.28032C-100000@mandrakesoft.mandrakesoft.com>
In-Reply-To: <Pine.LNX.3.96.1010218165420.28032C-100000@mandrakesoft.mandrakesoft.com>
Thanks to all,
I've just found http://www.linuxnewbie.org to be a good start point
Pedro
On Sunday 18 February 2001 23:57, Jeff Garzik wrote:
> On Sun, 18 Feb 2001, Pedro Diaz Jimenez wrote:
> > This is an typical mail from an experienced user-land programmer who
> > wants to help in kernel development ;D.
> >
> > I've been lurking for a while in this list and I'm wondering if this is
> > the right list for asking stupid newbie questions. Is it?. If not, do you
> > know one?. Where I can find documentation?
>
> We are always welcome to answer newbie -kernel hacking- questions...
> just ask specific ones. For example, ask "how does struct netdevice's
> last_rx member get used?", not "what do I need to do to write a network
> driver?"....
>
> The documentation is in linux/Documentation/*
>
he he
> > (yeah, yeah, read the code. But
> > things are always better with an 'vi Doc.txt' in the processes tree :)
>
> Really. The code is the best documentation. Hone your code reading
> skills. Use the source, Luke.
>
> Jeff
>
>
>
>
> -
> 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/
prev parent reply other threads:[~2001-02-18 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-18 22:47 Beware - kernel Newbie! Pedro Diaz Jimenez
2001-02-18 22:57 ` Jeff Garzik
2001-02-18 23:17 ` Pedro Diaz Jimenez [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=01021900174905.00315@tajo \
--to=pdiaz88@terra.es \
--cc=jgarzik@mandrakesoft.mandrakesoft.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