From: Andrew Ebling <aebling@tao-group.com>
To: michail@manegakis.freeserve.co.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: non-hackers
Date: 12 Dec 2001 07:57:50 +0000 [thread overview]
Message-ID: <1008143871.406.0.camel@spinel> (raw)
In-Reply-To: <E16DyWZ-0004uW-00.2001-12-12-01-49-32@mail5.svr.pol.co.uk>
In-Reply-To: <E16DyWZ-0004uW-00.2001-12-12-01-49-32@mail5.svr.pol.co.uk>
On Wed, 2001-12-12 at 01:49, Michael Menegakis wrote:
> Since I'm not a kernel expert and absolutely not a kernel hacker I'd like to
> submit my thoughts that may be proven usefull to all you maintainers. I
> believe there is a need for a message board that everyone could submit bugs
> of the kernel after being informed by a help file on how exactly this should
> be done.
There is plenty of information on this:
- in the Documentation directory in the kernel source.
- in the mailing list FAQ, the address of which appended to every post
to this list.
> I really don't feel we, the kernel users, should spend your valuable
> time and post these here, as well as we need a help site that tells us how
> exactly we should submit our kernel issues. And anyway, to be informed how we
> can recognize what is actually a bug and what is a user fault from an easy to
> read web site.
The "kernel users" should follow the instructions above, search the
archives (address is in FAQ), if the problem has not been reported,
report it, if it has been reported (and they have no more information to
add) they should not post and can rest assured that at least the hackers
know about it... a fix may even be iminent.
> I find it too difficult for us, the average kernel users, to have to read
> books and books of documendation - and eventually become hackers - when there
> would be a site that covers this step by step and doesn't need to much efford
> on research. Please let me know if you do care at all anyway, or you're only
> concerned about -your- bug discoveries (I'm not implying anything, let me
> add).
A quick search for "kernel hacking" on google brings up
http://www.kernelhacking.org
which contains a kernelhacking-HOWTO (work in progress) in the docs
section. It aims to make kernel hacking/programming/debugging
accessible to the average C programmer.
With a _little_ effort, you could have found all this information
yourself ;)
<RANT> <--- HTML tag from HTML 4.0-ac1 ;)
If the kernel doesn't currently do what _you_ want, _you_ should invest
_your_ time to learn how to make it do what you want, then contribute
your fix and what you learned in the process by helping others. That is
what free software is all about.
</RANT>
happy hacking,
Andy
prev parent reply other threads:[~2001-12-12 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 1:49 non-hackers Michael Menegakis
2001-12-12 7:57 ` Andrew Ebling [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=1008143871.406.0.camel@spinel \
--to=aebling@tao-group.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michail@manegakis.freeserve.co.uk \
/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