From: Antonio Vargas <wind@cocodriloo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel hcking
Date: Fri, 11 Apr 2003 17:34:59 +0200 [thread overview]
Message-ID: <20030411153459.GD25862@wind.cocodriloo.com> (raw)
In-Reply-To: <20030411170709.A33459@freebsdcluster.dk>
On Fri, Apr 11, 2003 at 05:07:09PM +0200, Vikram Rangnekar wrote:
>
> I'm a kernel newbie and just wanted to know what do most kernel hackers do
> when working on the kernel say 2.5 when you make changes do u need to
> recompile the kernel and reboot the machine to test your small modification
> or do people use something like bochs. Also every time you makes changes in
> the kernel it must be hell to recompile the whole thing do kernel hackers
> just compile the specific file and link it into the kernel or something. Some
> of these will be stupid questions to most of you but I am curious since I've
> been working on the kernel lately and recompiling and rebooting is driving me
> nuts
I'm also newbie at actually coding on the kernel, and I've
been using user-mode-linux to try my patches... it's easy and clean,
just make a very small config so that the initial compile is
also fast.
Then, when you are doing incremental compiling, just do a
"make -j linux", this is very fast when you are not recompiling
all .o files since the makefile checks the last-modified date
for the .c files.
For maximum performance, also use ccache with (very important) the
cache directory on the same filesystem than the compile directory.
I keep a "compile" directory and a "ccache" directory at the same
level.
When testing with user-mode-linux, you can simply type
./linux and the new kernel boots in your terminal. If
you want to boot a real machine, I suggest you get a
second computer and boot it by loading the kernel off
the net, using tftp protocol.
Ping me if you want some more help at this last issue.
Greets and have fun!
Antonio.
prev parent reply other threads:[~2003-04-11 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 15:07 kernel hcking Vikram Rangnekar
2003-04-11 15:17 ` Con Kolivas
2003-04-11 15:24 ` John Bradford
2003-04-11 15:37 ` Antonio Vargas
2003-04-11 16:00 ` John Bradford
2003-04-11 21:08 ` Jan-Benedict Glaw
2003-04-11 15:34 ` Antonio Vargas [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=20030411153459.GD25862@wind.cocodriloo.com \
--to=wind@cocodriloo.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