From: "tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: kernel code?
Date: Sun, 29 Jan 2006 01:14:45 -0800 [thread overview]
Message-ID: <000501c624b4$7288f7d0$ae1dae48@dataplus4puarg> (raw)
Hay,
I just got the latest code for the kernel.
I have a question,
I am trying to add some stuff, and make some programs that use some
functions in the kernel. I was looking at the kernel and am able to
understand what it does (with the functions and stuff) I get it, but, how do
you know where the functions and data types and structures are that you
want? I just don't know where to find everything that I need to code what I
want. I can code it, that is no problem for me, its just the tracking it
down. I haven't ever had something this big on my hands, and when I look at
all the files, they make some sense, but it looks a bit confusing as to what
does what, and where I should put what when I code it.
Also, when I type make, I get the following errors.
well. I got the error that there was no .config file, so I just created a
blank, because I didn't want to deal with it.
Do I have to write a file? if so, does someone know where I could get a
template on how/where to?
Also, upon compilation, will it compile for the computer I am on? I want it
to be cross-compatible.
Last thing. If I do get a successfull make, it won't replace the current
kernel will it?
Thanks,
Tyler Littlefield.
Check out our website:
http://tysplace.the-leetest.net
check out my blog:
livejournal.com/~tylerrl
[my programs don't have bugs, just randomly added features]
[failure is not an option, it comes bundled with windows!]
next reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
tyler [this message]
` ace
` Scott Howell
` Chris Norman
` Gregory Nowak
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='000501c624b4$7288f7d0$ae1dae48@dataplus4puarg' \
--to=compgeek13@gmail.com \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).