From: Alessandro Amici <alexamici@fastwebnet.it>
To: Miguel Angel Flores <maf@sombragris.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel development environment
Date: Sat, 4 Dec 2004 22:37:48 +0100 [thread overview]
Message-ID: <200412042237.48729.alexamici@fastwebnet.it> (raw)
In-Reply-To: <41B22381.10008@sombragris.com>
Miguel
On Saturday 04 December 2004 21:52, Miguel Angel Flores wrote:
> Alessandro Amici wrote:
> >At the very minimum you need to add grep to your tool set.
> >It will save you a lot of flames :)
>
> As I can see the kernel hacker tools are the standard GNU tools. I'm in
> the correct way ;)
Well, I'm not exactly a kernel hacker even if I did some minor driver work in
the past, so don't rate my advice too high :)
Anyhow, I lurk l-k regularly and most of the developing tools that appear in
discussions among real kernel hackers appear to be the standard GNU tools.
I did personally try out some of the open source IDE like sourcenav and
kdevelop, but the raw size of the kernel code pushed them to or beyond their
limits. That was a couple of years ago things may have changed.
Other stuff that come to mind are: a decent mailer (Mozilla Mail should
qualify :), a decent irc client, bk or if you prefer cvs. I saw ctags cited
at times, but I didn't use it myself.
Hope this helps,
Alessandro
www.b-open-solutions.it
next prev parent reply other threads:[~2004-12-04 21:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 17:52 kernel development environment Miguel Angel Flores
2004-12-04 17:56 ` Jan-Benedict Glaw
2004-12-04 20:21 ` Alessandro Amici
2004-12-04 20:52 ` Miguel Angel Flores
2004-12-04 21:37 ` Alessandro Amici [this message]
2004-12-04 21:47 ` Lee Revell
2004-12-04 21:40 ` Michal Schmidt
2004-12-04 22:45 ` Lee Revell
2004-12-04 23:37 ` Randy.Dunlap
2004-12-04 23:55 ` Lee Revell
2004-12-05 0:34 ` Michal Schmidt
2004-12-05 0:39 ` Lee Revell
2004-12-05 21:29 ` Baruch Even
2004-12-05 0:05 ` Jim Nelson
2004-12-16 1:35 ` Bill Davidsen
2004-12-04 21:58 ` Roger Luethi
2004-12-05 17:41 ` Alan Cox
2004-12-05 20:16 ` Herbert Poetzl
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=200412042237.48729.alexamici@fastwebnet.it \
--to=alexamici@fastwebnet.it \
--cc=linux-kernel@vger.kernel.org \
--cc=maf@sombragris.com \
/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