public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Antonio Vargas <wind@cocodriloo.com>
To: John Bradford <john@grabjohn.com>
Cc: Vikram Rangnekar <vicky@freebsdcluster.net>,
	linux-kernel@vger.kernel.org
Subject: Re: kernel hcking
Date: Fri, 11 Apr 2003 17:37:11 +0200	[thread overview]
Message-ID: <20030411153711.GE25862@wind.cocodriloo.com> (raw)
In-Reply-To: <200304111524.h3BFObYL001454@81-2-122-30.bradfords.org.uk>

On Fri, Apr 11, 2003 at 04:24:37PM +0100, John Bradford 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.
> 
> A lot of developers have multiple physical machines, which makes
> testing various different kernels a lot easier.
> 
> > Also every time you makes changes in the kernel it must be hell to
> > recompile the whole thing
> 
> If you are testing kernels on a separate machine to the one you are
> compiling on, and therefore not rebooting, it's not much of a problem
> - with enough RAM, most or all of the kernel source will be cached,
> and you can compile a kernel in three to five minutes on a fast
> machine.

John, you mean a "make clean && make bzImage" takes you only about 4
minutes??? I would like to know more details about .config, machine
specs, compiler and so on :)

And no doubt having enough RAM to cache all the tree is really good :)

Greets, Antonio.

  reply	other threads:[~2003-04-11 15:16 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 [this message]
2003-04-11 16:00     ` John Bradford
2003-04-11 21:08     ` Jan-Benedict Glaw
2003-04-11 15:34 ` Antonio Vargas

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=20030411153711.GE25862@wind.cocodriloo.com \
    --to=wind@cocodriloo.com \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vicky@freebsdcluster.net \
    /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