From: Borislav Petkov <bp@alien8.de>
To: Someone Something <fordhaivat@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Help for a newbie
Date: Sun, 13 Jun 2010 10:14:33 +0200 [thread overview]
Message-ID: <20100613081433.GA6428@liondog.tnic> (raw)
In-Reply-To: <AANLkTilzq64CPECxFb77PEdjv1Pcj72622rmhPchz9L8@mail.gmail.com>
From: Someone Something <fordhaivat@gmail.com>
Date: Sat, Jun 12, 2010 at 11:32:36PM -0400
> Hello. I am pretty new to the world of kernel hacking and I have a few
> questions. I have gotten myself a copy of Linux Kernel Development by
> robert love and I am also reading parts of the source code. Here are
> my current questions:
>
> 1) when you write userland apps, you usually include stuff like :
> sys/types.h or errono.h where are all these defined in the linux
> kernel because I would like to add a few syscalls of my own?
>
> 2) what are some bugs in the kernel that a beginner can fix?
>
> 3) is there any definitive guide to the kernel that you guys refer
> most newbies to? (like Programming Perl for perl)?
>
> 4) Where's the linux kernel headed to next? What higher level features
> (i.e. real features, not bug fixes) are going to implemented?
>
> Thanks a bunch.
>
> PS it'd be nice if you could CC me in the reply cause I don't think
> I've registered properly
http://kernelnewbies.org/ is the place you want to start - simply read
it all, cover to cover :)
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2010-06-13 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimmhzbgddTZBoaSy4iXpjB4Gdy6zTab0EjCM1IK@mail.gmail.com>
[not found] ` <AANLkTinwQ5tUDyHIObolQrd0jESH5PGEBKqwk6a_jHWK@mail.gmail.com>
[not found] ` <AANLkTilbMPLfd415EV32or8FZCM1sWi-RzeWtPAX95-o@mail.gmail.com>
2010-06-13 3:32 ` Someone Something
2010-06-13 8:14 ` Borislav Petkov [this message]
2010-06-13 13:29 ` Valdis.Kletnieks
2010-06-13 17:03 ` Someone Something
2010-06-13 22:47 ` Someone Something
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=20100613081433.GA6428@liondog.tnic \
--to=bp@alien8.de \
--cc=fordhaivat@gmail.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
all inboxes | Powered by JetHome®